1615310 - Crash in [@ OOM | unknown | NS_ABORT_OOM | XPCJSContext::Initialize]

Status: RESOLVED WONTFIX

(Core :: JavaScript Engine, defect)

Description

[Pascal Chevrel:pascalc]

This bug is for crash report bp-cfbdfbcb-5be5-47e5-ab2e-ec7860200213.

Top 10 frames of crashing thread:

0 xul.dll NS_ABORT_OOM xpcom/base/nsDebugImpl.cpp:608
1 xul.dll XPCJSContext::Initialize js/xpconnect/src/XPCJSContext.cpp:1274
2 xul.dll static XPCJSContext::NewXPCJSContext js/xpconnect/src/XPCJSContext.cpp:1307
3 xul.dll static nsXPConnect::InitJSContext js/xpconnect/src/nsXPConnect.cpp:74
4 xul.dll NS_InitXPCOM xpcom/build/XPCOMInit.cpp:489
5 xul.dll XRE_InitEmbedding2 toolkit/xre/nsEmbedFunctions.cpp:200
6 xul.dll mozilla::ipc::ScopedXREEmbed::Start ipc/glue/ScopedXREEmbed.cpp
7 xul.dll mozilla::dom::ContentProcess::Init dom/ipc/ContentProcess.cpp:188
8 xul.dll XRE_InitChildProcess toolkit/xre/nsEmbedFunctions.cpp:744
9 xul.dll mozilla::BootstrapImpl::XRE_InitChildProcess toolkit/xre/Bootstrap.cpp:67

There is a spike in 74.0b1/b2 with this signature and they seem to be startup crashes which means user loss.

Comment 1

[Andrew McCreight [:mccr8]]

Probably an unactionable OOM...

Comment 2

[Ted Campbell [:tcampbell]]

These OOMs mean there isn't enough memory to start critical pieces of the engine. They can occur for either parent or child process. This is similar to other types of small-OOM crashes we get.

Comment 3

[Andrew McCreight [:mccr8]]

(In reply to Pascal Chevrel:pascalc from comment #0)

There is a spike in 74.0b1/b2 with this signature and they seem to be startup crashes which means user loss.

Do we distinguish content process startup from main process startup? If somebody has like a million tabs open, and opens another and it crashes, that's a lot less bad than a crash when we start the browser. The stack in comment 0 is the content process, but I'm not sure if we can tell if there's other content processes that have successfully started or not.

Comment 4

[Andrew McCreight [:mccr8]]

I looked at a few of these crashes. They had an okay amount of memory available (like 500MB to 1GB), but very little page file, on the order of a couple of MB.