Closed
Bug 1385540
Opened 8 years ago
Closed 4 years ago
Crash in JSAtom::hash
Categories
(Core :: JavaScript Engine, defect, P3)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jseward, Unassigned)
Details
(Keywords: crash)
Crash Data
This bug was filed from the Socorro interface and is
report bp-7a1baff1-f41c-49d1-a2ed-9c6b00170728.
=============================================================
This is topcrash #6 in the Windows nightly of 20170727162801.
In fact I can only see two distinct installations, but still I don't
think we should crash here.
Reporter | ||
Updated•8 years ago
|
Flags: needinfo?(jdemooij)
Comment 1•8 years ago
|
||
(In reply to Julian Seward [:jseward] from comment #0)
> In fact I can only see two distinct installations, but still I don't
> think we should crash here.
A lot of these are nullptr crashes and with a very low uptime. The URLs are not useful.
No idea how we get nullptr atoms there. Maybe OOM but we do a lot of OOM fuzzing. We are working on some changes to environment objects that might help but I doubt it...
Flags: needinfo?(jdemooij)
![]() |
||
Comment 2•8 years ago
|
||
Relatively low volume in FF56 and very low after. Not actionable at them movement. Will revisit priority if that changes.
Comment 3•7 years ago
|
||
Closing because no crashes reported for 12 weeks.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Comment 4•7 years ago
|
||
There are still some crashes so reopen it.
Comment 5•4 years ago
|
||
Closing because no crashes reported for 12 weeks.
Status: REOPENED → RESOLVED
Closed: 7 years ago → 4 years ago
Resolution: --- → WORKSFORME
Updated•4 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•