Closed Bug 1046044 Opened 10 years ago Closed 10 years ago

"Reddit Enhancement Suite" add-on does not work with e10s

Categories

(Firefox :: Extension Compatibility, defect)

34 Branch
x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME
Tracking Status
e10s + ---

People

(Reporter: kaankasim88, Unassigned)

References

Details

(Keywords: addon-compat)

Extension doesn't load at all.
kaankasim, thanks for testing. I'll update our list of add-ons.
Blocks: e10s-addons
Mentor: cpeterson
tracking-e10s: --- → +
Keywords: addon-compat
Status: UNCONFIRMED → NEW
Ever confirmed: true
does anyone have specifics on what sorts of errors there are yet, etc?  I'd certainly like to get this resolved (I'm the core author of RES)
kaankasim, can you please share any error messages you see logged in Firefox's Browser Console?

Steve, you can enable e10s in Nightly channel builds be flipping the about:config pref "browser.tabs.remote.autostart" to true and restarting Firefox. When e10s is enabled, add-ons run in the parent/chrome process by default. Because RES modifies web content, you will need to add code that runs in the content/child process sandbox.

MDN also has a good introduction to e10s for add-on developers. If you have any more questions, just drop by the #e10s IRC channel on irc.mozilla.org.

https://developer.mozilla.org/en-US/Add-ons/Working_with_multiprocess_Firefox
There is nothing on the console other than "Use of getPreventDefault() is deprecated.  Use defaultPrevented instead." which shows in non e10s window too.  It is from res though, it doesn't show up  when disabled.
I'm not finding any interesting/useful error messages, all I'm getting is:

System JS : ERROR resource://gre/modules/AddonManager.jsm:20 - Error: You cannot use the AddonManager in child processes!

that's not my code, of course, and I'm not directly referencing AddonManager, nor is there any sort of interesting / useful trace that can tell me what I'm using that's referencing the AddonManager.

Any tips on further debugging would be appreciated.
You will need to move any RES code that reads or modifies web content to "frame scripts" that run in the sandboxed content process. The best place to get help is on #e10s IRC channel on irc.mozilla.org. MDN has more more information here:

https://developer.mozilla.org/en-US/Add-ons/Working_with_multiprocess_Firefox

Yes, the AddonManager error message is unrelated to your code.
RES appears to be using jetpack, which has known issues with e10s

Specifically, their onContent hook for inserting pagemods is broken:
http://dxr.mozilla.org/mozilla-central/source/addon-sdk/source/lib/sdk/page-mod.js#48

So there's not much point worrying about brokenness in jetpack addons until bug 930164 is resolved (and we should mention that before telling any addon authors to fix their stuff)
Depends on: 930164
See Also: → 801977
RES actually works for me (36.0a1 (2014-11-23) on OS X).
Thanks for testing Alexander. This addon was probably fixed by some recent e10s changes to improve addon compatibility.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
FYI, it's broken again in 2015-02-22's Nightly. From what the debugger says, the add-on is completely missing from the source list, so probably not loaded at all. All is fine in a non-e10s window, though.
And it works again in 2015-02-26's Nightly.
Depends on: 1134137
You need to log in before you can comment on or make changes to this bug.