1870398 - Crash in [@ InitializeJS] with "js::jit::InitializeJit() failed"

Status: NEW

(Core :: JavaScript Engine: JIT, defect, P4)

Description

[Andrew McCreight [:mccr8]]

Crash report: https://crash-stats.mozilla.org/report/index/38870e29-3c7b-4465-a86a-35aa00231214

MOZ_CRASH Reason: js::jit::InitializeJit() failed

Top 10 frames of crashing thread:

0  libxul.so  MOZ_Crash  mfbt/Assertions.h:281
0  libxul.so  InitializeJS  xpcom/build/XPCOMInit.cpp:237
0  libxul.so  NS_InitXPCOM  xpcom/build/XPCOMInit.cpp:434
1  libxul.so  ScopedXPCOMStartup::Initialize  toolkit/xre/nsAppRunner.cpp:1995
1  libxul.so  XREMain::XRE_main  toolkit/xre/nsAppRunner.cpp:5914
2  libxul.so  XRE_main  toolkit/xre/nsAppRunner.cpp:5974
3  firefox-bin  do_main  browser/app/nsBrowserApp.cpp:227
3  firefox-bin  main  browser/app/nsBrowserApp.cpp:445
4  libc.so.6  __libc_start_call_main  sysdeps/nptl/libc_start_call_main.h:58
5  libc.so.6  __libc_start_main_alias_1  csu/libc-start.c:360

This doesn't seem like it is particularly actionable, and we may have a bug on file for this kind of start up failure on file already, but I'm filing one in case we don't.

Comment 1

[Matthew Gaudet (he/him) [:mgaudet]]

So this specific crash is telling us js::jit::InitializeJit() failed (but not more detail there) -- it can fail with TLS context init failure or executable memory process init.

Looking at the general table of init failures:

1 js::jit::InitializeJit() failed 74 67.89 %
2 ICU4CLibrary::Initialize() failed 32 29.36 %
3 js::CreateHelperThreadsState() failed 1 0.92 %
4 js::frontend::WellKnownParserAtoms::initSingleton() failed 1 0.92 %

None of these seem particularly actionable, so setting low priority.