Closed Bug 855903 Opened 12 years ago Closed 12 years ago

CC unlinking can trigger GC

Categories

(Core :: XPCOM, defect)

Product:
Core
Component:
XPCOM
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: mccr8, Unassigned)

References

Details

I think I've seen this before when messing around with ICC stuff in a try run, and it seems like it would be pretty bad from a pause perspective. My theory would be that we're triggering a JS_ContextDestroy with a GC, or something... It wouldn't be that hard to instrument the browser GC callbacks to assert if we're in the middle of a CC to figure out what is happening.
I investigated this and I found that it was the fault of a nasty bit of code in nsXPConnect::CheckForDebugMode that allocates and destroys a JSContext. bholley is going to clean it up, which should fix this problem.
Depends on: 872135
Summary: CC unlinking can trigger GC? → CC unlinking can trigger GC
I guess I'll just mark this WFM.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.