Open
Bug 2041307
Opened 6 days ago
Updated 5 days ago
Crash in [@ js::BarrieredBase<T>::unbarrieredSet]
Categories
(Core :: JavaScript Engine, defect, P3)
Tracking
()
NEW
People
(Reporter: aryx, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: crash)
Crash Data
Firefox crash new in version 151. In total 28 crash reports including from development versions.
Jonco: Is this new or a signature change from bug 2025288?
Crash report: https://crash-stats.mozilla.org/report/index/d4fc6d5c-d6e1-465f-82ed-e117e0260521
Reason:
EXCEPTION_ACCESS_VIOLATION_WRITE
Top 10 frames:
0 xul.dll js::BarrieredBase<JSFunction*>::unbarrieredSet(JSFunction* const&) js/src/gc/Barrier.h:494
0 xul.dll js::gc::BarrieredPtrImpl<JSFunction*, 11>::init(JSFunction* const&) js/src/gc/Barrier.h:594
0 xul.dll js::FunctionScope::initCanonicalFunction(JSFunction*) js/src/vm/Scope.h:746
0 xul.dll JSScript::fullyInitFromStencil(JSContext*, js::frontend::CompilationAtomCache... js/src/vm/JSScript.cpp:2672
0 xul.dll JSScript::fromStencil(JSContext*, js::frontend::CompilationAtomCache&, js::fr... js/src/vm/JSScript.cpp:2729
0 xul.dll InstantiateScriptStencils(JSContext*, js::frontend::CompilationAtomCache&, js... js/src/frontend/Stencil.cpp:2394
0 xul.dll js::frontend::CompilationStencil::instantiateStencilAfterPreparation(JSContex... js/src/frontend/Stencil.cpp:2896
1 xul.dll js::frontend::CompilationStencil::instantiateStencils(JSContext*, js::fronten... js/src/frontend/Stencil.cpp:2807
2 xul.dll js::frontend::InitialStencilAndDelazifications::instantiateStencils(JSContext... js/src/frontend/Stencil.cpp:4138
2 xul.dll InstantiateStencilsImpl<js::frontend::InitialStencilAndDelazifications>(JSCon... js/src/frontend/BytecodeCompiler.cpp:469
Flags: needinfo?(jcoppeard)
Comment 1•6 days ago
|
||
Started happening on March 24 right when bug 2025288 landed so timing is right.
Only three crashes have the stack trace above. The others are a bunch of different things. This is probably the usual bad hardware issue.
Flags: needinfo?(jcoppeard)
You need to log in
before you can comment on or make changes to this bug.
Description
•