1657825 - Crash in [@ WasmTrapHandler]

Status: RESOLVED FIXED

(Core :: JavaScript: WebAssembly, defect)

Description

[Mayank Bansal]

This bug is for crash report bp-e33408af-d8e4-429f-82b0-789a90200807.

Top 5 frames of crashing thread:

0 xul.dll WasmTrapHandler js/src/wasm/WasmSignalHandlers.cpp:765
1 ntdll.dll RtlpCallVectoredHandlers 
2 ntdll.dll RtlDispatchException 
3 ntdll.dll KiUserExceptionDispatch 
4  @0x2bdfe4a892a 

STR: I was trying to profile from https://battle.wazana.io/ , when I got this error on the profiler page

Comment 1

[Gerald Squelart (he/him) (not at Mozilla since 2022-09-15)]

(In reply to Mayank Bansal from comment #0)

This bug is for crash report bp-e33408af-d8e4-429f-82b0-789a90200807.

Not much info in the report. 😕

STR: I was trying to profile from https://battle.wazana.io/ , when I got this error on the profiler page

Could you please clarify the STR?
"I got this error on the profiler page", as in, you captured the profile, got to profiler.firefox.com, and there it crashed? Can you remember how far you got on the profiler page (compared to successful profiling)?

Comment 2

[Markus Stange [:mstange]]

The profiler front-end uses asm.js and wasm in the following places:

• When opening the profiler, asm.js is used for uncompressing from gzip. Sometimes wasm is used to demangle function names (but I think we don't hit this path on Windows unless you profile a local build).
• When sharing a profile, asm.js is used for compressing to gzip.

These crashes indicate bugs in the JS engine and not in the profiler.

Comment 3

[Mayank Bansal]

(In reply to Gerald Squelart [:gerald] (he/him) from comment #1)

(In reply to Mayank Bansal from comment #0)

This bug is for crash report bp-e33408af-d8e4-429f-82b0-789a90200807.

Not much info in the report. 😕

STR: I was trying to profile from https://battle.wazana.io/ , when I got this error on the profiler page

Could you please clarify the STR?
"I got this error on the profiler page", as in, you captured the profile, got to profiler.firefox.com, and there it crashed? Can you remember how far you got on the profiler page (compared to successful profiling)?

I captured the profile on page https://battle.wazana.io/, went to profiler.firefox.com, and while the profile was being symbolicated/compressed, I clicked on the "upload"/"share" button. After a few seconds, profiler.firefox.com crashed

Comment 4

[Markus Stange [:mstange]]

Bug 1657917 is about a similar crash on macOS.

Comment 5

[Markus Stange [:mstange]]

This is probably a regression from bug 1639153, which has already been backed out, so this should be fixed.