Closed Bug 1405383 Opened 2 years ago Closed 1 year ago

Crash in OOM | large | NS_ABORT_OOM | nsTArray_base<T>::EnsureCapacity<T> | nsTArray_Impl<T>::AppendElements<T> | gfxPlatformFontList::AddGenericFonts

Categories

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

57 Branch
Unspecified
Windows 10
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox57 + fix-optional

People

(Reporter: yoasif, Unassigned, NeedInfo)

References

Details

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

Crash Data

This bug was filed from the Socorro interface and is 
report bp-60a149be-2032-44b6-97ff-5e1370171003.
=============================================================

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.
Jonathan, this appears to be a large OOM (30GB allocation) during font loading.  Any thoughts what is going on here?
Flags: needinfo?(jfkthame)
The crash is /probably/ related to me having, like, a thousand tabs open under tree-style-tabs. I heard that beta had /better/ unloaded tab support, so I'm not sure about that. It was crashing a lot, including just on the new tab page, so it wasn't any specific site.
Even with a thousand tabs, it makes no sense that we'd try to allocate such a ridiculous amount of memory during font loading. I'm suspicious that either there's something unusual about the system environment that is confusing us, or an unrelated bug has trashed one of the arrays involved here, making it appear to be vastly bigger than it should be.

chc4000, do you know of anything unusual about your system and how fonts are managed (e.g. some 3rd-party font management software that might be involved)?

Does it help if you turn off the "Enable multi-process" checkbox in the browser options?
Flags: needinfo?(jfkthame)
There are other crashes than just the array. I've also gotten crashes pointing to a font hashmap iterator (https://crash-stats.mozilla.com/report/index/96030cda-5ba1-411a-858c-ca80a0171003) and hashmap allocation (https://crash-stats.mozilla.com/report/index/233d0d79-5d81-416d-a09d-b561d0171003).

This is just a vanilla Windows 10 install. No fonts specially installed, no font management, etc.

I disabled `browser.tabs.remote.autostart` (and `browser.tabs.remote.autostart.2`) and restarted: it just spins while I try to startup, not updating the URL bar when I type in it unless I move the window (and the window moving itself is laggy) until it crashes with https://crash-stats.mozilla.com/report/index/7235f06b-a516-4618-8c62-13ad10171003. Is there another config I could try? This is with the Quantum Beta, not Nightly.
See Also: → 1405385
See Also: → 1405381
(In reply to chc4000 from comment #4)
> There are other crashes than just the array. I've also gotten crashes
> pointing to a font hashmap iterator
> (https://crash-stats.mozilla.com/report/index/96030cda-5ba1-411a-858c-
> ca80a0171003) and hashmap allocation
> (https://crash-stats.mozilla.com/report/index/233d0d79-5d81-416d-a09d-
> b561d0171003).
> 
> This is just a vanilla Windows 10 install. No fonts specially installed, no
> font management, etc.
> 
> I disabled `browser.tabs.remote.autostart` (and
> `browser.tabs.remote.autostart.2`) and restarted: it just spins while I try
> to startup, not updating the URL bar when I type in it unless I move the
> window (and the window moving itself is laggy) until it crashes with
> https://crash-stats.mozilla.com/report/index/7235f06b-a516-4618-8c62-
> 13ad10171003. Is there another config I could try? This is with the Quantum
> Beta, not Nightly.

Can you try running Firefox in Safe Mode? Running with a fresh profile? You're clearly running into something very broken, but currently I have no real clue what the underlying problem is.
Flags: needinfo?(chc4000)
Priority: -- → P1
Whiteboard: [gfx-noted]
We can track this for 57, but even with the info here and in the possibly related bugs there may not be anything actionable yet.
I looked at the crash volume and the crash sign is very low volume. Marking this as fix-optional for that reason.
(In reply to Jonathan Kew (:jfkthame) from comment #5)
> ... 
> Can you try running Firefox in Safe Mode? Running with a fresh profile?
> You're clearly running into something very broken, but currently I have no
> real clue what the underlying problem is.

I emailed chc4000 in September - doesn't reply.

This and bug 1405385 are basically gone after the early versions of 60. bug 1405381 however remains.

https://crash-stats.mozilla.com/search/?signature=~gfxPlatformFontList%3A%3ALookupInFaceNameLists&date=>%3D2018-11-23T08%3A18%3A03.000Z&date=<2018-12-23T08%3A18%3A03.000Z&_sort=-date&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-signature
Flags: needinfo?(chc4000) → needinfo?(jfkthame)

Closing because no crashes reported for 12 weeks.

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