Closed Bug 1660073 Opened 5 years ago Closed 1 year ago

Crash in [@ OOM | unknown | NS_ABORT_OOM | nsPresArena<T>::Allocate]

Categories

(Core :: Layout, defect)

77 Branch
All
Windows
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox-esr68 --- unaffected
firefox-esr78 --- affected
firefox79 --- wontfix
firefox80 --- fix-optional

People

(Reporter: philipp, Unassigned)

Details

(Keywords: crash, regression)

Crash Data

This bug is for crash report bp-3240a9b5-6e4a-4f1e-b09b-b745f0200819.

Top 10 frames of crashing thread:

0 xul.dll NS_ABORT_OOM xpcom/base/nsDebugImpl.cpp:620
1 xul.dll nsPresArena<32768, mozilla::DisplayListArenaObjectId, 88>::Allocate layout/base/nsPresArena.cpp
2 xul.dll nsIFrame::DisplayBackgroundUnconditional layout/generic/nsFrame.cpp:2663
3 xul.dll nsIFrame::DisplayBorderBackgroundOutline layout/generic/nsFrame.cpp:2695
4 xul.dll mozilla::ScrollFrameHelper::BuildDisplayList layout/generic/nsGfxScrollFrame.cpp:3422
5 xul.dll nsIFrame::BuildDisplayListForChild layout/generic/nsFrame.cpp:4359
6 xul.dll mozilla::ViewportFrame::BuildDisplayList layout/generic/ViewportFrame.cpp:63
7 xul.dll nsIFrame::BuildDisplayListForStackingContext layout/generic/nsFrame.cpp:3528
8 xul.dll static nsLayoutUtils::GetFramesForArea layout/base/nsLayoutUtils.cpp:3343
9 xul.dll static nsLayoutUtils::GetFrameForPoint layout/base/nsLayoutUtils.cpp:3301

crash reports with this signature are starting to show up since firefox 77.

A lot of the crashes seem to be on Win7/2GB systems, but there are also some Win10/4GB, which is sad... I wonder if there's any possibility we could degrade more gracefully here when memory is tight, rather than simply crashing?

Severity: -- → S3

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.