1698279 - Crash in [@ OOM | small]

Status: RESOLVED DUPLICATE of bug 1673778

(Core :: General, defect, P3)

Description

[Worcester12345]

Crash report: https://crash-stats.mozilla.org/report/index/0ebb0f9d-760b-4317-8e79-ebeba0210313

MOZ_CRASH Reason: MOZ_CRASH()

Top 10 frames of crashing thread:

0 mozglue.dll mozalloc_abort memory/mozalloc/mozalloc_abort.cpp:33
1 mozglue.dll mozalloc_handle_oom memory/mozalloc/mozalloc_oom.cpp:51
2 xul.dll static nsINode::operator new dom/base/nsINode.cpp:136
3 xul.dll NS_NewHTMLSharedElement dom/html/HTMLSharedElement.cpp:25
4 xul.dll static nsContentDLF::CreateBlankDocument layout/build/nsContentDLF.cpp:255
5 xul.dll nsDocShell::CreateAboutBlankContentViewer docshell/base/nsDocShell.cpp:6795
6 xul.dll nsDocShell::EnsureContentViewer docshell/base/nsDocShell.cpp:6643
7 xul.dll nsDocShell::GetDocument docshell/base/nsDocShell.cpp:3240
8 xul.dll nsGlobalWindowOuter::WrapObject dom/base/nsGlobalWindowOuter.h:230
9 xul.dll static XPCConvert::NativeData2JS js/xpconnect/src/XPCConvert.cpp:355

Comment 1

[Worcester12345]

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:87.0) Gecko/20100101 Firefox/87.0 ID:20210311161514

Comment 2

[Chris Peterson [:cpeterson]]

This "OOM | small" crashes are caused by running out of available memory. They're is not really actionable without a reproducible test case. Running out of memory is not fault of the DOM Navigation code that failed to allocate memory in the stack trace in comment 0. The cause of the out of memory could be a memory leak or heavy web page. I don't think we have a meta bug for "OOM | small" crashes, but I will resolve as a duplicate of "OOM | small" bug 1673778.