Closed Bug 1641305 Opened 4 years ago Closed 4 years ago

Crash in [@ EmitBodyExprs(`anonymous namespace'::FunctionCompiler&)]

Categories

(Core :: JavaScript: WebAssembly, defect, P3)

76 Branch
Unspecified
Windows 10
defect

Tracking

()

RESOLVED INACTIVE

People

(Reporter: yoasif, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug is for crash report bp-e7f12427-649d-41ed-83e3-0e4f80200527.

Top 10 frames of crashing thread:

0 xul.dll EmitBodyExprs js/src/wasm/WasmIonCompile.cpp:3916
1 xul.dll js::wasm::IonCompileFunctions js/src/wasm/WasmIonCompile.cpp:4703
2 xul.dll ExecuteCompileTask js/src/wasm/WasmGenerator.cpp:735
3 xul.dll js::wasm::ExecuteCompileTaskFromHelperThread js/src/wasm/WasmGenerator.cpp:761
4 xul.dll js::HelperThread::handleWasmWorkload js/src/vm/HelperThreads.cpp:2071
5 xul.dll static js::HelperThread::ThreadMain js/src/vm/HelperThreads.cpp:2048
6 xul.dll static js::detail::ThreadTrampoline<void  js/src/threading/Thread.h:206
7 ucrtbase.dll thread_start<unsigned int , 1> 
8 kernel32.dll BaseThreadInitThunk 
9 ntdll.dll RtlUserThreadStart 

Reported on: https://www.reddit.com/r/firefox/comments/grns5s/twitchtv_and_protonmail_broking_firefox/

User said they saw this on two different sites:

Crash Id: ID: e7f12427-649d-41ed-83e3-0e4f80200527 Protonmail
Crash Id: 83829ba9-889f-49cc-99d7-0e2740200527 Twitch.TV

Crash-stats says SIGILL for the first one, which is a pretty weird exception to get at that location (compiled C++ code, not jitted code).

Intel(R) Celeron(R) CPU G3900 @ 2.80GHz (family 6 model 94 stepping 3) cpucount=8 (presumably quad hyperthreaded), Nvidia card. This is confusing since the Web says the CPU is dual-core hyperthreaded with no SMP capability and integrated graphics.

Twitch I know for a fact uses wasm. Protonmail may use asm.js for their crypto library (github.com/openpgpjs), which just funnels into wasm in our engine.

Severity: -- → S3
Priority: -- → P3

No further crash reports from anywhere to correlate with this one, most likely a one-off.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.