1784107 - Crash in [@ js::frontend::WellKnownParserAtoms::initSingle]

Status: NEW

(Core :: JavaScript Engine, defect, P5)

Description

[Chris Peterson [:cpeterson]]

Crash report: https://crash-stats.mozilla.org/report/index/a174f005-24b6-4d26-bdd8-983750220810

This is a very low volume crash during parent process startup. We have crash reports from Windows, Linux, and Android.

Reason: SIGSEGV / SEGV_MAPERR

Top 10 frames of crashing thread:

0 libxul.so js::frontend::WellKnownParserAtoms::initSingle js/src/frontend/ParserAtom.cpp:1218
1 libxul.so js::frontend::WellKnownParserAtoms::init js/src/frontend/ParserAtom.cpp:1237
2 libxul.so JSRuntime::initializeParserAtoms js/src/frontend/ParserAtom.cpp:1270
3 libxul.so JS::InitSelfHostedCode js/src/vm/Initialization.cpp:220
4 libxul.so XPCJSContext::NewXPCJSContext js/xpconnect/src/XPCJSContext.cpp:1420
5 libxul.so nsXPConnect::InitJSContext js/xpconnect/src/nsXPConnect.cpp:88
6 libxul.so XREMain::XRE_main toolkit/xre/nsAppRunner.cpp:5894
7 libxul.so XRE_main toolkit/xre/nsAppRunner.cpp:5962
8 libxul.so GeckoStart toolkit/xre/nsAndroidStartup.cpp:54
9 libxul.so mozilla::BootstrapImpl::GeckoStart toolkit/xre/Bootstrap.cpp:78

Comment 1

[Nicolas B. Pierron [:nbp]]

This looks like a start-up issue where the binary memory would have been corrupted.
Most likely a disk/download issue.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

Since the crash volume is low (less than 5 per week), the severity is downgraded to S3. Feel free to change it back if you think the bug is still critical.

For more information, please visit auto_nag documentation.