Closed Bug 1405385 Opened 7 years ago Closed 5 years ago

Crash in OOM | large | NS_ABORT_OOM | PLDHashTable::Add | gfxPlatformFontList::LookupInFaceNameLists

Categories

(Core :: Graphics: Text, defect, P2)

57 Branch
Unspecified
Windows 10
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox57 - affected

People

(Reporter: yoasif, Unassigned)

References

Details

(Keywords: crash, Whiteboard: [gfx-noted])

Crash Data

This bug was filed from the Socorro interface and is 
report bp-814f7d2d-f197-46a8-9ea0-ef02c0171003.
=============================================================

Reported on Twitter: https://twitter.com/chc40/status/915222046191292418

switched to firefox quantum, used it for five minutes, got three full crashes and a tab crash already. good job.
Another crazy allocation (3GB).
See Also: → 1405383
Priority: -- → P1
Whiteboard: [gfx-noted]
Jonathan, is it really expected for the initial hash table alloc to be 2-3GB?  Most of these are from a single user, but still, anything that would explain this?  Perhaps a rogue preference or some bad bit somewhere?
Flags: needinfo?(jfkthame)
No, this seems vastly beyond what is reasonable. Currently I don't really have any theories as to what might have caused it. I've asked the user (in bug 1405383) to see if Safe Mode or a fresh profile makes any difference.
Flags: needinfo?(jfkthame)
This sounds bad, but I don't think it will help the investigation for release management to track this bug. Tracking in bug 1405383 instead.

Closing because no crashes reported for 12 weeks.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.