Crash in [@ OOM | unknown | js::AutoEnterOOMUnsafeRegion::crash | js::wasm::Init]
Categories
(Core :: JavaScript: WebAssembly, defect, P3)
Tracking
()
People
(Reporter: sefeng, Unassigned)
Details
(Keywords: crash)
Crash Data
This bug is for crash report bp-a72dbcdf-fb29-441f-ab77-bedef0200706.
Top 10 frames of crashing thread:
0 xul.dll js::AutoEnterOOMUnsafeRegion::crash js/src/vm/JSContext.cpp:1194
1 xul.dll js::wasm::Init js/src/wasm/WasmProcess.cpp:382
2 xul.dll JS::detail::InitWithFailureDiagnostic js/src/vm/Initialization.cpp:169
3 xul.dll NS_InitXPCOM xpcom/build/XPCOMInit.cpp:441
4 xul.dll XRE_InitEmbedding2 toolkit/xre/nsEmbedFunctions.cpp:197
5 xul.dll mozilla::ipc::ScopedXREEmbed::Start ipc/glue/ScopedXREEmbed.cpp
6 xul.dll mozilla::dom::ContentProcess::Init dom/ipc/ContentProcess.cpp:181
7 xul.dll XRE_InitChildProcess toolkit/xre/nsEmbedFunctions.cpp:710
8 firefox.exe content_process_main ipc/contentproc/plugin-container.cpp:56
9 firefox.exe NS_internal_main browser/app/nsBrowserApp.cpp:303
Looks like this is a crash that we expect which we can learn from the call stack.
Comment 1•4 years ago
|
||
This is likely a result of bug 1547649, a change in (OOM) signature but not a new issue.
Updated•4 years ago
|
Comment 2•4 years ago
|
||
Yeah, this is not a bug, it's a deliberate panic resulting from no memory available in a situation where propagating the OOM is pointless -- we'll panic with a less descriptive error subsequently.
Not sure what the proper resolution is here -- close as WONTFIX or INVALID? Leave it open but lower it to P5? These panics are common during testing but we're not going to attempt to fix anything here.
Comment 3•4 years ago
|
||
I think closing as WONTFIX/INVALID would be the appropriate thing to do since we don't actually consider this a bug/defect
Updated•4 years ago
|
Comment 4•2 years ago
|
||
MANY multiple crashes pointing at this one today.
Comment 5•2 years ago
|
||
Crash signatures?
Comment 6•2 years ago
|
||
I just cleared them all. I thought you see those on your end. Thanks anyhow.
Comment 7•2 years ago
|
||
For what it's worth, I'm sure there will be plenty more coming.
Description
•