Closed
Bug 606068
Opened 14 years ago
Closed 3 months ago
Integrate XPConnect with per-compartment GC
Categories
(Core :: XPConnect, defect)
Core
XPConnect
Tracking
()
RESOLVED
WORKSFORME
| Tracking | Status | |
|---|---|---|
| status2.0 | --- | wanted |
People
(Reporter: gal, Unassigned)
References
Details
This bug probably needs sub-bugs. We have to mark xpconnect roots when we do a per-compartment GC. We might need new GC callbacks for this. We want to mark all the wrappers, but only those in a specific compartment.
|
||
Updated•14 years ago
|
blocking2.0: ? → beta8+
|
|
||
Updated•14 years ago
|
blocking2.0: beta8+ → beta9+
|
Reporter | |
Comment 1•14 years ago
|
||
No longer have to block on this. We will force all threads to synchronize even
if we only GC a single compartment.
|
|
Reporter | |
Updated•14 years ago
|
No longer blocks: compartmentGC
|
Assignee | |
Updated•10 years ago
|
Assignee: general → nobody
|
||
Comment 2•10 years ago
|
||
Black marking in XPConnect is very much not a bottleneck now that bindings has mostly replaced it.
|
||
Updated•2 years ago
|
Severity: normal → S3
|
||
Comment 4•3 months ago
|
||
Like comment 2 says, we don't have nearly as many of these with the new bindings. In addition, I think some work has been done to break up XPConnect wrappers a bit by compartment after they showed up in profiles. If there's more that needs to be done because things are showing up in a profile, we can file new bugs for the specific issues.
Status: NEW → RESOLVED
Closed: 3 months ago
Component: JavaScript Engine → XPConnect
Flags: needinfo?(continuation)
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•