Crash in js::TypeScript::destroy
Categories
(Core :: JavaScript Engine: JIT, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox63 | --- | unaffected |
firefox64 | --- | unaffected |
firefox65 | --- | fix-optional |
firefox66 | --- | affected |
People
(Reporter: calixte, Unassigned)
References
(Blocks 1 open bug)
Details
(4 keywords, Whiteboard: [#jsapi:crashes-retriage])
Crash Data
Comment 1•6 years ago
|
||
Updated•6 years ago
|
Comment 2•6 years ago
|
||
Comment 3•6 years ago
|
||
addresses are semi-randomish (often things like 0x2000000, but also true wildptrs (https://crash-stats.mozilla.com/report/index/31febb6b-a3c7-4af8-bd24-e9f050181224)).
Should be re-triaged
Comment 4•6 years ago
|
||
nbp: We should re-triage this bug as suggested jesup
Comment 5•6 years ago
|
||
Looking at the addresses, these look like a bunch of bit-flips, with a single exception reported in comment 3.
The volume being that low, I do not think we should re-triage it unless we see more crashes like comment 3, but that would not make them more actionable either.
Updated•6 years ago
|
Comment 6•5 years ago
|
||
This is not actionable.
Volume is even lower starting with Firefox 66.
Comment 7•4 years ago
|
||
Removing employee no longer with company from CC list of private bugs.
Comment 8•4 years ago
|
||
Volume has been near-zero for a long time and code is now removed from tree entirely. We didn't learn much here so closing bug.
Comment 9•4 years ago
|
||
Since the bug is closed, the stalled keyword is now meaningless.
For more information, please visit auto_nag documentation.
Updated•1 year ago
|
Description
•