Closed
Bug 1514280
Opened 7 years ago
Closed 7 years ago
Crash in mozilla::detail::HashTable<T>::Iterator::Iterator | js::jit::JitActivation::~JitActivation
Categories
(Core :: JavaScript Engine: JIT, defect)
Tracking
()
RESOLVED
INVALID
| Tracking | Status | |
|---|---|---|
| firefox-esr60 | --- | unaffected |
| firefox64 | --- | unaffected |
| firefox65 | --- | unaffected |
| firefox66 | --- | affected |
People
(Reporter: calixte, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: crash, regression)
Crash Data
This bug was filed from the Socorro interface and is
report bp-5430065f-914d-4b18-98c8-6e1440181214.
=============================================================
Top 10 frames of crashing thread:
0 libxul.so mozilla::detail::HashTable<mozilla::HashMapEntry<unsigned char*, JS::GCVector<js::jit::RematerializedFrame*, 0ul, js::TempAllocPolicy> >, mozilla::HashMap<unsigned char*, JS::GCVector<js::jit::RematerializedFrame*, 0ul, js::TempAllocPolicy>, mozilla::DefaultHasher<unsigned char*>, js::TempAllocPolicy>::MapHashPolicy, js::TempAllocPolicy>::Iterator::Iterator mfbt/HashTable.h:1694
1 libxul.so js::jit::JitActivation::~JitActivation mfbt/HashTable.h:1402
2 libxul.so js::jit::MaybeEnterJit js/src/jit/Jit.cpp:106
3 libxul.so js::RunScript js/src/vm/Interpreter.cpp:408
4 libxul.so js::InternalCallOrConstruct js/src/vm/Interpreter.cpp:563
5 libxul.so InternalConstruct js/src/vm/Interpreter.cpp:636
6 libxul.so js::jit::DoCallFallback js/src/vm/Interpreter.cpp:679
7 @0x98be4dd2cf7
8 @0x7fe05f5baf2f
9 @0x98be4dce4de
=============================================================
There is 1 crash in nightly 66 with buildid 20181214054322. In analyzing the backtrace, the regression may have been introduced by patch [1] to fix bug 1508873.
[1] https://hg.mozilla.org/mozilla-central/rev?node=95e3de1d6643
Flags: needinfo?(nfroyd)
Comment 1•7 years ago
|
||
I think this is just a signature change; we have a number of pre-existing crashes under JitActivation::~JitActivation. But it does look like somebody is accessing a null pointer that they shouldn't be...?
Component: MFBT → JavaScript Engine: JIT
Flags: needinfo?(nfroyd)
Comment 2•7 years ago
|
||
Last crash was in 2018121405432.
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•