Closed
Bug 705771
Opened 13 years ago
Closed 13 years ago
hangs in nsAttrAndChildArray::Clear()
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: mccr8, Unassigned)
References
Details
(Keywords: hang)
Crash Data
These hangs mostly show up in the CC, but there are a couple in the GC. I think for the CC, this will be fixed by bug 652781. This is the only hang I've seen so far in the CC.
The CC stacks all look like this:
0 nsAttrAndChildArray::Clear
1 nsGenericElement::~nsGenericElement
2 nsHTMLAnchorElement::`scalar deleting destructor'
3 nsNodeUtils::LastRelease
4 nsGenericElement::Release
5 nsCycleCollector::CollectWhite
https://crash-stats.mozilla.com/report/index/f56364eb-fed5-4fe1-96d0-ed5052111126
One GC stack looks like this:
0 nsAttrAndChildArray::Clear
1 nsImageLoadingContent::~nsImageLoadingContent
2 nsGenericElement::~nsGenericElement
3 nsHTMLImageElement::`scalar deleting destructor'
4 nsGenericElement::Release
5 DoDeferredRelease<nsISupports* __ptr64>
6 XPCJSRuntime::GCCallback
7 js_GC
https://crash-stats.mozilla.com/report/index/8fc49bae-2ddd-46da-aaa5-5bb992111126
another GC stack looks like this:
0 nsAttrAndChildArray::Clear
1 nsGenericElement::~nsGenericElement
2 nsSVGGraphicElement::~nsSVGGraphicElement
3 nsSVGPathElement::~nsSVGPathElement
4 nsSVGPathElement::`scalar deleting destructor'
5 nsNodeUtils::LastRelease
6 nsGenericElement::Release
7 XPC_WN_NoHelper_Finalize
8 js::gc::Arena::finalize<JSObject>
9 js::gc::FinalizeTypedArenas<JSObject>
10 js::gc::ArenaLists::finalizeObjects
11 SweepPhase
12 MarkAndSweep
13 GCCycle
14 js_GC
https://crash-stats.mozilla.com/report/index/4715cb87-7ac7-40ae-a2f2-c5ac92111126
Updated•13 years ago
|
Severity: normal → critical
Reporter | ||
Comment 1•13 years ago
|
||
This style of hang detector seems to be obsolete, so I think it makes sense to close these hangs, and file new reports for things the new hang detector finds.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•