-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Firefox] Wasavi painfully slow with e10s #144
Comments
Thank you. |
Doesn't seem to work :( Although it's not your fault. From the browser console:
Which is not supported yet according to Are We WebExtensions Yet?. A quick search on Bugzilla pointed me to bug 1320862. Going from the Wasavi code, it seems like this has something to do with sync. Is there an easy way to disable it? I don't need (nor want) to sync anything. |
Thanks, it's a step closer to working in Firefox! Now the issue is that I would try this myself, since the change seems trivial, but I didn't manage to build the add-on. I installed npm, ran |
Looks like we're still a way off. Firefox also doesn't support |
I added the document about build and test wasavi: It is not mandatory to build xpi to develop wasavi. Install web-ext with npm, and
The command launches Firefox for debugging with built-in wasavi. |
I just tested the latest unstable release, and it works great on Nightly! Thanks :) |
When using in an e10s (multi-process) enabled Firefox build, Wasavi slows down the entire browser to a crawl. This is probably due to excessive usage of CPOWs.
More information on https://developer.mozilla.org/en-US/Add-ons/Working_with_multiprocess_Firefox and https://developer.mozilla.org/en-US/Firefox/Multiprocess_Firefox/Limitations_of_chrome_scripts
The text was updated successfully, but these errors were encountered: