Open
Bug 1192301
Opened 9 years ago
Updated 1 year ago
[meta] Bring Order to Chaos (in the GC)
Categories
(Core :: JavaScript: GC, defect)
Core
JavaScript: GC
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox42 | --- | affected |
People
(Reporter: terrence, Unassigned)
References
(Depends on 6 open bugs, Blocks 2 open bugs)
Details
(Keywords: meta)
Our GC algorithm is a data-flow maze. In theory we have tight bounds on the valid lifetimes and values of the various inter-slice states, yet in practice we poke and prod these from all over the place to the point that they are effectively all just globals. For most state this isn't a huge issue, but for things like incrementalState and mode that are poked and prodded from literally everywhere, in every thread, constantly, this lack of discipline is quite worrying. The basic plan is to (1) salve some of the most egregious dataflow issues by passing data manually as many places as possible to increase our density of pure code and (2) to reformat the GC in such a way that we don't need to retain so much inter-slice state. I have some speculative ideas for this that I want to experiment with.
Updated•8 years ago
|
Updated•3 years ago
|
Assignee: terrence.d.cole → nobody
Status: ASSIGNED → NEW
Updated•1 year ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•