Closed
Bug 516518
(electrolysis)
Opened 15 years ago
Closed 11 years ago
Overall Electrolysis Tracking
Categories
(Core Graveyard :: Tracking, defect)
Core Graveyard
Tracking
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: benjamin, Assigned: benjamin)
References
Details
(Keywords: meta)
This bug is designed to collect the various Electrolysis projects. Please do not comment in it at all. To ask questions about Electrolysis use the mozilla.dev.tech.dom newsgroup.
Assignee | ||
Updated•15 years ago
|
Alias: electrolysis
Updated•13 years ago
|
tracking-firefox7:
--- → ?
Updated•13 years ago
|
tracking-firefox7:
? → ---
(In reply to comment #0) > This bug is designed to collect the various Electrolysis projects. Please do > not comment in it at all. To ask questions about Electrolysis use the > mozilla.dev.tech.dom newsgroup. 1) Where is the Electrolysis project listed/defined? 2) how do I access the mozilla.dev.tech.dom newgroup. I used to be able to access both news.mozilla.org and news.mozdev.org, but now I get timeouts on both. Is it located in one of those places? Are they publicly connectible or how do I find / access that group? Thanks!
Comment 7•13 years ago
|
||
(In reply to comment #6) > 1) Where is the Electrolysis project listed/defined? > 2) how do I access the mozilla.dev.tech.dom newgroup. > > I used to be able to access > both news.mozilla.org > and news.mozdev.org, but now I get timeouts on both. > > Is it located in one of those places? Are they publicly connectible or how > do I find / access that group? > > > Thanks! 1) https://wiki.mozilla.org/Electrolysis 2) http://groups.google.com/group/mozilla.dev.tech.dom/topics?pli=1
Assignee | ||
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INCOMPLETE
Comment 16•11 years ago
|
||
Okay, so all further improvements were abandoned?
Comment 17•11 years ago
|
||
Perhaps under this label, I know that bug #392073, filed in 2006 had been dependent on this, but is now listed as re-opened. It covered the problem of non-parallel execution of multiple threads which as some have pointed out is likely due to some 'big locks' being held to prevent parallel execution. Is it 'known' howmany big locks are potential blockers? Is there any code around the locks to track time spent waiting for each lock? Instrumenting the code might be the first step to identifying where work needs to be done.
Comment 18•11 years ago
|
||
I don't see why we should close this bug now?
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Assignee | ||
Comment 19•11 years ago
|
||
Because we aren't tracking this project any more.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → INCOMPLETE
Comment 20•11 years ago
|
||
According to https://wiki.mozilla.org/Electrolysis, the project has been revived. Should this be reopened?
Comment 21•11 years ago
|
||
(In reply to replicator.snail from comment #20) > According to https://wiki.mozilla.org/Electrolysis, the project has been > revived. Should this be reopened? I think they are tracking the progress of the Electrolysis project in two new bugs now: https://bugzilla.mozilla.org/show_bug.cgi?id=fxe10s https://bugzilla.mozilla.org/show_bug.cgi?id=core-e10s So this bug should not be reopened.
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•