Closed Bug 705717 Opened 13 years ago Closed 13 years ago

possible hangs in presshell memory reporter

Categories

(Core :: Layout, defect)

Product:
Core
Component:
Layout
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: mccr8, Unassigned)

References

Details

(Keywords: hang)

Crash Data

here's an example report: https://crash-stats.mozilla.com/report/index/4c759e4c-0345-4495-9a88-d25cf2111128 (click show other threads to see the thread where the actual hang was happening) Not very common, but it is the only memory-reporter related hang I've found so far, and given how rarely people must actually run about:memory, it seems like this could be common. I didn't see any of the other functions in the stack for this memory reporter that show up in the top 100 crash/hangs.
Severity: normal → critical
presshell memory reporter (PresShell::MemoryReporter::SizeEnumerator) seems to be a frequent cause of hangs during PL_DHashTableEnumerate. I looked at 16 of these hangs, and all but 3 involved PresShell::MemoryReporter::SizeEnumerator. here's an example: https://crash-stats.mozilla.com/report/index/823539fb-88a6-4cf3-a1e4-dcdd62111126
Crash Signature: [@ chromehang | nsPresArena::Size() ] → [@ chromehang | nsPresArena::Size() ] [@ chromehang | PL_DHashTableEnumerate ]
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
Product: Core → Core Graveyard
Component: Layout: Misc Code → Layout
Product: Core Graveyard → Core
You need to log in before you can comment on or make changes to this bug.