Skip to content
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

Multiprocess Firefox (e10s) #18

Closed
lidel opened this issue Apr 12, 2015 · 3 comments
Closed

Multiprocess Firefox (e10s) #18

lidel opened this issue Apr 12, 2015 · 3 comments
Labels
kind/discussion Topical discussion; usually not changes to codebase kind/maintenance Work required to avoid breaking changes or harm to project's status quo
Milestone

Comments

@lidel
Copy link
Member

lidel commented Apr 12, 2015

Electrolysis, also known as e10s, is the next major compatibility change coming to Firefox. In a nutshell, Firefox will run on multiple processes now, running each content tab in a different one. This should improve responsiveness and overall stability, but it also means many add-ons will need to be updated to support this.

We will be talking more about these changes in this blog in the future. For now we recommend you start looking at the available documentation.

https://blog.mozilla.org/addons/2015/04/08/add-ons-update-63/

@lidel lidel added the kind/discussion Topical discussion; usually not changes to codebase label Apr 12, 2015
@lidel lidel added kind/maintenance Work required to avoid breaking changes or harm to project's status quo and removed kind/discussion Topical discussion; usually not changes to codebase labels Aug 26, 2015
@lidel
Copy link
Member Author

lidel commented Aug 26, 2015

First step is to set up TravisCI target that runs tests with e10s enabled:
https://wiki.mozilla.org/Electrolysis#Enabling_and_Disabling_Electrolysis

@lidel
Copy link
Member Author

lidel commented Aug 27, 2015

Running tests with Nightly does not seem to be a worthy effort: cfx builder does not support e10s (running unsigned addon requires setting xpinstall.signatures.required=false etc).

Mozilla mentioned that they will provide an unbranded browser version that has signature verification disabled and can be used for development and tests:

An unbranded version of Firefox 42 should be available when 42 reaches beta.
https://groups.google.com/forum/#!topic/mozilla.addons.user-experience/GX3yQBS4o6s

I plan to wait for it and update Travis config around that time.

Good news is that I've manually run tests on current Nightly (43.0a1) and all passed.
Seems that chrome shims are enough for it to work without change.

But just in case shims are changed in future, some materials on e10s for future reference:

@lidel lidel changed the title Working with multiprocess Firefox Multiprocess Firefox (e10s) Aug 27, 2015
@lidel lidel added the kind/discussion Topical discussion; usually not changes to codebase label Aug 27, 2015
@lidel lidel mentioned this issue Aug 28, 2015
9 tasks
@lidel lidel added this to the v2.0.0 milestone Sep 9, 2015
@lidel
Copy link
Member Author

lidel commented Nov 27, 2015

Closed by #26

@lidel lidel closed this as completed Nov 27, 2015
@lidel lidel modified the milestones: v1.4.0, v2.0.0 Jan 3, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/discussion Topical discussion; usually not changes to codebase kind/maintenance Work required to avoid breaking changes or harm to project's status quo
Projects
None yet
Development

No branches or pull requests

1 participant