Closed
Bug 847418
Opened 12 years ago
Closed 12 years ago
Error: Module: sdk/private-browsing/utils has no authority to load: ../deprecate d/window-utils
Categories
(Add-on SDK Graveyard :: General, defect)
Add-on SDK Graveyard
General
Tracking
(Not tracked)
RESOLVED
FIXED
1.14
People
(Reporter: ochameau, Assigned: ochameau)
References
Details
Attachments
(1 file)
We are facing a regression from bug 793925.
In case the xpi contains the SDK (no --strip-sdk argument given) and being run on FF 21+, we are seeing following exception:
Error: Module: sdk/private-browsing/utils has no authority to load: ../deprecate
d/window-utils
sdk/private-browsing/utils 107
Traceback (most recent call last):
File "resource://gre/modules/NetUtil.jsm", line 140, in
aCallback(pipe.inputStream, aStatusCode, aRequest);
File "resource://gre/modules/commonjs/sdk/net/url.js", line 49, in
resolve(data);
... huge promise stack ...
That exception happens because we are checking for manifest entries for modules shipped in firefox. That breaks because the manifest is build for the precise SDK version shipped in the xpi and not for the one shipped in firefox. So that if you build a xpi with sdk master in will fail on current nightly/aurora as SDK dependencies are different.
We have to somehow ignore the manifest when we are using SDK modules from firefox.
Assignee | ||
Comment 1•12 years ago
|
||
Here is a simple workaround where we do not need to patch loader.
We can also modify cuddlefish and ignore sdk modules there,
but we would have to pass the info about "are we using firefox modules or not?" from bootstrap to cuddlefish.
Assignee: nobody → poirot.alex
Attachment #720704 -
Flags: review?(rFobic)
Assignee | ||
Updated•12 years ago
|
Severity: normal → critical
Updated•12 years ago
|
Attachment #720704 -
Flags: review?(rFobic) → review+
Comment 2•12 years ago
|
||
Commits pushed to master at https://github.com/mozilla/addon-sdk
https://github.com/mozilla/addon-sdk/commit/1a36e16a346b852e6e9d97b6d10641e10a7c462a
Bug 847418: Do not ship with manifest entries for SDK modules.
https://github.com/mozilla/addon-sdk/commit/6f0f31839ac5111f461aabe48f2ff48a50ded206
Merge pull request #831 from ochameau/sdk-entries
Bug 847418: Do not ship with manifest entries for SDK modules. r=@gozala
Assignee | ||
Comment 3•12 years ago
|
||
Needs to be uplifted to 1.14 in order to avoid being broken with ff21+ when not using --strip-sdk option.
Target Milestone: --- → 1.14
Assignee | ||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 4•12 years ago
|
||
Commit pushed to stabilization at https://github.com/mozilla/addon-sdk
https://github.com/mozilla/addon-sdk/commit/3aeed3202173975a5e6d42c34997909053abb2e7
Merge pull request #831 from ochameau/sdk-entries
Bug 847418: Do not ship with manifest entries for SDK modules. r=@gozala(cherry picked from commit 6f0f31839ac5111f461aabe48f2ff48a50ded206)
Conflicts:
test/private-browsing/windows.js
Comment 5•12 years ago
|
||
Commits pushed to integration at https://github.com/mozilla/addon-sdk
https://github.com/mozilla/addon-sdk/commit/1a36e16a346b852e6e9d97b6d10641e10a7c462a
Bug 847418: Do not ship with manifest entries for SDK modules.
https://github.com/mozilla/addon-sdk/commit/6f0f31839ac5111f461aabe48f2ff48a50ded206
Merge pull request #831 from ochameau/sdk-entries
You need to log in
before you can comment on or make changes to this bug.
Description
•