Closed Bug 684098 Opened 15 years ago Closed 14 years ago

ExplainLiveExpectedGarbage hangs the browser with DEBUG_CC

Categories

(Core :: XPCOM, defect)

defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: mccr8, Unassigned)

Details

When DEBUG_CC is defined, the browser gets hung in ExplainLiveExpectedGarbage, printing huge amounts of console spew about various marked JS objects that it says it didn't expect to find live. I assume the problem is that there's something it finds live that it doesn't expect (like a window) that ends up being reachable from a huge portion of the JS heap, and it is just taking a really long time enumerating it all. Commenting out the line that pushes the successor of a node onto the stack (queue.Push(target)) around line 3090 keeps the browser from being hung. I don't think it has always done this, but I haven't really used full-on DEBUG_CC in months, so I couldn't tell you when this started. Not really relatedly, but with DEBUG_CC there's a ton of console spew like this: nsCycleCollector: nsNodeInfo (XUL) keyset object @0x106a40a60 is still alive after calling RootAndUnlinkJSObjects, Unlink, and Unroot on it! This probably means the Unlink implementation was insufficient. nsCycleCollector: nsNodeInfo (XUL) menubar object @0x106a40b70 is still alive after calling RootAndUnlinkJSObjects, Unlink, and Unroot on it! This probably means the Unlink implementation was insufficient. nsCycleCollector: nsGenericElement (xhtml) a object @0x1447cf210 is still alive after calling RootAndUnlinkJSObjects, Unlink, and Unroot on it! This probably means the Unlink implementation was insufficient. nsCycleCollector: nsBaseContentList object @0x126f925c0 is still alive after calling RootAndUnlinkJSObjects, Unlink, and Unroot on it! This probably means the Unlink implementation was insufficient. nsCycleCollector: nsBindingManager object @0x1239654f0 is still alive after calling RootAndUnlinkJSObjects, Unlink, and Unroot on it! This probably means the Unlink implementation was insufficient. I don't know if that is meaningful or not. That doesn't cause the browser to hang at least. Browser still doesn't have shutdown leaks. I'll try to investigate some of these messages and see if they are meaningful.
ExplainLiveExpectedGarbage has been removed.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.