Closed
Bug 1378365
Opened 7 years ago
Closed 6 years ago
Crash in js::jit::GetNativeDataPropertyByValue<T>
Categories
(Core :: JavaScript Engine: JIT, defect, P5)
Tracking
()
RESOLVED
DUPLICATE
of bug 1502853
Tracking | Status | |
---|---|---|
firefox-esr52 | --- | unaffected |
firefox54 | --- | unaffected |
firefox55 | --- | wontfix |
firefox56 | --- | wontfix |
firefox57 | --- | wontfix |
firefox58 | --- | wontfix |
firefox59 | --- | ? |
People
(Reporter: philipp, Unassigned)
Details
(Keywords: crash, regression)
Crash Data
This bug was filed from the Socorro interface and is
report bp-6853e173-520b-42c5-8ff6-655920170705.
=============================================================
Crashing Thread (0)
Frame Module Signature Source
0 xul.dll js::jit::GetNativeDataPropertyByValue<1>(JSContext*, JSObject*, JS::Value*) js/src/jit/VMFunctions.cpp:1668
1 xul.dll NewObject js/src/jsobj.cpp:679
2 xul.dll EnterIon js/src/jit/Ion.cpp:2804
3 xul.dll js::TraceNullableRoot<js::Shape*>(JSTracer*, js::Shape**, char const*) js/src/gc/Marking.cpp:526
4 xul.dll js::TypeScript::SetArgument(JSContext*, JSScript*, unsigned int, js::TypeSet::Type) js/src/vm/TypeInference-inl.h:669
5 xul.dll js::jit::IonCannon(JSContext*, js::RunState&) js/src/jit/Ion.cpp:2902
6 @0xffffff81
crash reports with this signature are showing up cross-platform since version 55, the first one in 55.0a1 build 20170327030203. maybe that's related to bug 1328140?
Flags: needinfo?(jdemooij)
Comment 1•7 years ago
|
||
(gonna fix-optional for 55 due to low volume)
Updated•7 years ago
|
Priority: -- → P5
Comment 2•7 years ago
|
||
Too late for a fix for 56, crash is still fairly low volume.
Comment 3•7 years ago
|
||
Low volume, mostly Android, I don't see anything actionable. Probably not worth spending a lot of time on this right now.
Flags: needinfo?(jdemooij)
Comment 4•7 years ago
|
||
status-firefox59:
--- → ?
Comment 5•6 years ago
|
||
This is now tracked under a different signature.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•