705730 - hang in nsMemoryReporterManager::GetExplicit while iterating over arenas and cells

Status: RESOLVED INCOMPLETE

(Core :: JavaScript Engine, defect)

Description

[Andrew McCreight [:mccr8]]

Looks like I spoke too soon in bug 705717: here's another hang report in a memory reporter.  I looked at a dozen hang-crashes with this signature and they all had this stack:

0	js::gc::ForEachArenaAndCell<js::IterateArenaCallbackOp,js::IterateCellCallbackOp>
1	js::IterateCompartmentsArenasCells
2	mozilla::xpconnect::memory::CollectCompartmentStatsForRuntime
3	XPConnectJSCompartmentsMultiReporter::CollectReports
4	nsMemoryReporterManager::GetExplicit

here's an example: https://crash-stats.mozilla.com/report/index/b77588d9-5f98-48f2-9966-182f72111126

Comment 1

[Andrew McCreight [:mccr8]]

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.