Closed
Bug 1828949
Opened 2 years ago
Closed 2 years ago
Crash in [@ js::jit::MacroAssembler::passABIArg]
Categories
(Core :: JavaScript Engine: JIT, defect, P5)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: cpeterson, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: crash)
Crash Data
The first crash report with this signature was from Fenix 104.2.0. The crash volume is very low, but there are 168 crash reports in Fenix 112 from one device. Maybe there is a hardware problem with that user's device?
Crash report: https://crash-stats.mozilla.org/report/index/9b62aa9b-a575-4a23-913c-77a920230417
Reason: SIGSEGV / SEGV_MAPERR
Top 10 frames of crashing thread:
0 libxul.so js::jit::MacroAssembler::passABIArg js/src/jit/MacroAssembler.cpp:3706
1 libxul.so js::jit::MacroAssembler::passABIArg js/src/jit/MacroAssembler-inl.h:136
1 libxul.so js::jit::MacroAssembler::generateBailoutTail js/src/jit/MacroAssembler.cpp:2860
2 libxul.so js::jit::JitRuntime::generateBailoutTailStub js/src/jit/arm/Trampoline-arm.cpp:830
2 libxul.so js::jit::JitRuntime::generateTrampolines js/src/jit/Ion.cpp:142
2 libxul.so js::jit::JitRuntime::initialize js/src/jit/Ion.cpp:110
3 libxul.so JSRuntime::createJitRuntime js/src/vm/Realm.cpp:113
4 libxul.so JS::InitSelfHostedCode js/src/vm/Initialization.cpp:233
5 libxul.so XPCJSContext::Initialize js/xpconnect/src/XPCJSContext.cpp:1377
5 libxul.so XPCJSContext::NewXPCJSContext js/xpconnect/src/XPCJSContext.cpp:1413
Comment 1•2 years ago
|
||
The bug is linked to a topcrash signature, which matches the following criterion:
- Top 10 AArch64 and ARM crashes on release (startup)
For more information, please visit auto_nag documentation.
Keywords: topcrash,
topcrash-startup
Comment 2•2 years ago
|
||
Having a single person crashing ~160 times does not qualify at making this bug a top-crasher from my point of view.
This might well be a corrupted install.
Blocks: sm-defects-crashes
Status: NEW → RESOLVED
Closed: 2 years ago
Keywords: topcrash,
topcrash-startup
Resolution: --- → WORKSFORME
Updated•2 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•