Bug 648125 added support for cache for js loaded with loadSubScript. Somehow (probably because so many scripts just fail in the xpcshell harness used to generate jsloader cache), it was never exercised until bug 697762 landed. Now, there is a jssubloader/185/resource/gre/chrome/toolkit/content/global/devtools/dbg-transport.js that ends up packaged. That file should obviously be in omni.jar.

Do you want to dupe bug 732649 to this or vice versa?

Please can you set the target milestone when landing on inbound, along the lines of http://blog.bonardo.net/2012/03/23/how-you-can-help-mozilla-inbound-sheriffs-when-pushing :-) https://hg.mozilla.org/mozilla-central/rev/68def3ab33b6

Comment on attachment 606639 [details] [diff] [review] Package jssubloader cache in omnijar [Approval Request Comment] Regression caused by combination of bug 648125 and bug 697762 User impact if declined: extra unused file shipped in tarballs/installers Risk to taking this patch (and alternatives if risky): none String changes made by this patch: none

Comment on attachment 606639 [details] [diff] [review] Package jssubloader cache in omnijar [Triage Comment] Doesn't sound like this is absolutely necessary from the user's perspective, but given where we are in Aurora this should be OK to land.

(In reply to Mike Hommey [:glandium] from comment #10) > https://hg.mozilla.org/integration/mozilla-inbound/rev/5a5a55d435ca https://hg.mozilla.org/mozilla-central/rev/5a5a55d435ca