1664308 - Crash in [@ OOM | unknown | NS_ABORT_OOM | XPCJSContext::NewXPCJSContext]

Status: NEW

(Core :: XPConnect, defect, P3)

Description

[Sean Feng [:sefeng211]]

Crash report: https://crash-stats.mozilla.org/report/index/b8660e25-c740-4b86-8474-9d4730200829

Top 10 frames of crashing thread:

0 xul.dll NS_ABORT_OOM xpcom/base/nsDebugImpl.cpp:620
1 xul.dll static XPCJSContext::NewXPCJSContext js/xpconnect/src/XPCJSContext.cpp:1339
2 xul.dll xpc::InitializeJSContext js/xpconnect/src/nsXPConnect.cpp:95
3 xul.dll NS_InitXPCOM xpcom/build/XPCOMInit.cpp:491
4 xul.dll XRE_InitEmbedding2 toolkit/xre/nsEmbedFunctions.cpp:197
5 xul.dll mozilla::ipc::ScopedXREEmbed::Start ipc/glue/ScopedXREEmbed.cpp:79
6 xul.dll mozilla::dom::ContentProcess::Init dom/ipc/ContentProcess.cpp:201
7 xul.dll XRE_InitChildProcess toolkit/xre/nsEmbedFunctions.cpp:710
8 firefox.exe wmain toolkit/xre/nsWindowsWMain.cpp:131
9 firefox.exe __scrt_common_main_seh /builds/worker/workspace/obj-build/browser/app/f:/dd/vctools/crt/vcstartup/src/startup/exe_common.inl:288

They are valid OOM crashes since the available page file is low.

Comment 1

[Andrew McCreight (out of office until 8/21) [:mccr8]]

I'm not sure why we aren't getting an OOM size. Maybe we're too early in startup for crash annotations to work.

Comment 2

[Pascal Chevrel:pascalc]

When the bug was filed 7 months ago we had 10 to 20 crashes a day for this signature, now we have 70 to 100.

Comment 4

[Andrew McCreight (out of office until 8/21) [:mccr8]]

I looked at a couple crashes, and they had very little available page file, around 10 to 30 MB. I'm not sure if there's anything we can really do in that case.