Closed
Bug 516752
(e10s)
Opened 15 years ago
Closed 8 years ago
[meta] Electrolysis for Firefox tracking
Categories
(Core Graveyard :: Tracking, defect)
Core Graveyard
Tracking
Tracking
(relnote-firefox 40+)
RESOLVED
FIXED
mozilla48
Tracking | Status | |
---|---|---|
relnote-firefox | --- | 40+ |
People
(Reporter: benjamin, Unassigned)
References
(Depends on 32 open bugs)
Details
(Keywords: feature, meta)
This bug is for tracking the requirements of getting Firefox running with content processes (tabs). Please do not comment in this bug. Use the mozilla.dev.tech.dom newsgroup to ask questions or make comments.
Updated•15 years ago
|
Depends on: e10s-necko
Reporter | ||
Updated•14 years ago
|
Assignee: benjamin → dolske
Comment 4•13 years ago
|
||
Electrolysis development seems to be picking up as i see more articles about it recently. Any ballpark estimate of when it'll be final and released? Firefox 10-12?
Updated•13 years ago
|
Updated•11 years ago
|
Alias: e10s
Updated•11 years ago
|
Assignee: dolske → gavin.sharp
Comment 8•11 years ago
|
||
Bug 516518 depends on Bug 646596 but should instead be linked here. Probably, there are other bugs in Bug 516518 that should be moved here, too.
Updated•11 years ago
|
Depends on: e10s-addons
Updated•11 years ago
|
Depends on: e10s-social
Updated•11 years ago
|
OS: Windows NT → All
Hardware: x86 → All
Updated•11 years ago
|
Updated•11 years ago
|
Depends on: metrofxe10s
Updated•10 years ago
|
Depends on: e10s-ime-tsf
Comment 11•10 years ago
|
||
Anyone using the Larch disposable branch for this project? https://tbpl.mozilla.org/?tree=Larch I tried reaching billm for an answer since he was the last person commiting back in August 12. Can I take this branch and make it available for other teams?
Comment 12•10 years ago
|
||
armenzg: I don't believe billm or any other e10s developer is using the Larch branch any longer, so feel free to reset it. I will update the disposable project branch wiki's booking table.
Comment 13•10 years ago
|
||
Thank you Chris!
Comment 14•10 years ago
|
||
Hi, I found that bug: 'Bug 392073 - Firefox limited to 1 CPU on multi-cpu machine; multi-threading appears broken' is duplicate if this bug. I think that my Firefox since many versions uses only one CPU. I now realized it, but it seems I always suspected it. It was like this on OSX Snow Leopard, OSX Lion, OSX Maverics. Now I use Firefox 27.0.1 on OSX Maverics. I think this 1 CPU problem is the source of every think I don't like in current Firefox, like being slow, and slow again. Surprisingly nobody says it. It shocked me a little bit when I realized it. Can somebody confirm me that it is true? I think this can be main cause of serious Firefox decrease in market share. I am still shocked.
Comment 15•10 years ago
|
||
Lukasz: Firefox has been multi-threaded for many years. Firefox's threads should be able to use more than one CPU today. This bug is about splitting Firefox into multiple processes, not multi-threading. If you see Firefox only using one CPU, please file a new bug report.
Depends on: 974332
Depends on: e10s-tests
Updated•10 years ago
|
No longer depends on: metrofxe10s
Updated•10 years ago
|
Depends on: old-e10s-m2
No longer depends on: 687194
Comment 16•10 years ago
|
||
Can this bug be given a better name? The definition of electrolysis barely even fits the task at hand, nor is it a term that anyone outside of the Firefox dev team (and perhaps even within it) would use while searching for this. As such, it's really no wonder that there have been a myriad of duplicate bugs filed for this.
No longer depends on: 1019560
Updated•10 years ago
|
Assignee: gavin.sharp → nobody
Depends on: 997631
Comment 17•10 years ago
|
||
These signatures just appeared recently and i think they are OMTC related since the crashing doesn't occur when i'm in the beta channel bp-fadccfe0-b2d8-4ff0-9dc4-c3bef2140723 7/23/2014 12:27 AM 049fda77-7c7a-4aa6-8b56-5374aa267c9f 7/22/2014 9:01 PM bce26a99-779b-4af8-96c9-7db7e0ec6880 7/21/2014 11:05 PM bp-e58ca647-2d08-45f4-8250-6bc412140721 7/21/2014 11:04 PM 05a6f156-895a-40c6-b477-edda6fd31662 7/21/2014 10:59 PM d61c896c-7a03-48b9-bf37-8d8b5d21ba61 7/20/2014 3:11 PM bp-33299aab-6896-4a0a-adab-68fab2140719 7/19/2014 4:46 PM 31a72c8b-3afd-427c-b916-6b13ffdfdc8e 7/19/2014 4:36 PM bp-4f96564f-55f5-4321-9a50-d786b2140719 7/19/2014 4:32 PM
No longer depends on: 1042965
Updated•10 years ago
|
Depends on: e10s-harness
Comment 19•10 years ago
|
||
Sry for the dupes, I didn't see there was another tracking bug like bug 997462...
Depends on: e10s-lazarus
No longer depends on: e10s-lazarus
Depends on: e10s-lazarus
No longer depends on: 1068400
Depends on: 1143235
Comment 21•9 years ago
|
||
f12 cannot make whole screen capture under e10s mode.
Comment 22•9 years ago
|
||
We are going to enable e10s to aurora soon: https://wiki.mozilla.org/Electrolysis#Schedule Release Note Request (optional, but appreciated) [Why is this notable]: I don't think I need to explain why e10s is important. [Suggested wording]: Multi-process (aka Electrolysis or e10s) enabled by default [Links (documentation, blog post, etc)]: I guess we will have a few blog posts about it.
relnote-firefox:
--- → ?
This is not on by default now for aurora, but I'd like to still give it a release note if that seems good to the e10s team. Brad and jimm, what do you think? Do you have something to link to and a suggested wording?
Flags: needinfo?(jmathies)
Flags: needinfo?(blassey.bugs)
Comment 24•9 years ago
|
||
"Process separation enabled for opt-in testing in Dev-edition"
Flags: needinfo?(blassey.bugs)
Thanks Brad. I linked the note to the MDN page: https://developer.mozilla.org/en-US/Firefox/Multiprocess_Firefox
Updated•9 years ago
|
Flags: needinfo?(jmathies)
Comment 26•9 years ago
|
||
new depend bug 1174027
Updated•9 years ago
|
Updated•9 years ago
|
Updated•9 years ago
|
QA Contact: chofmann
Updated•9 years ago
|
Summary: Electrolysis for Firefox tracking → [meta] Electrolysis for Firefox tracking
Blocks: 975193
Updated•8 years ago
|
Updated•8 years ago
|
Comment 29•8 years ago
|
||
e10s is the standard mode for shipping up to beta, and should be out on release in 48. Closing this tracker out since we aren't using it.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla48
Assignee | ||
Updated•8 years ago
|
Product: Core → Core Graveyard
Updated•7 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•