Closed
Bug 1290388
Opened 8 years ago
Closed 7 years ago
Crash in js::FrameIter::functionDisplayAtom
Categories
(Core :: JavaScript Engine, defect, P3)
Tracking
()
RESOLVED
INVALID
People
(Reporter: marco, Unassigned)
References
Details
(4 keywords)
Crash Data
Attachments
(1 file)
113.88 KB,
image/png
|
Details |
This bug was filed from the Socorro interface and is
report bp-58df47b0-8173-4c70-80c3-4f5b62160728.
=============================================================
This startup crash has been spiking recently on Beta 48.
As you can see from the correlations image, it's only happening with the latest beta build (2016-07-25), on Windows XP and with a particular AMD CPU (AuthenticAMD family 16 model 6 stepping 3 | 2).
It's now the #27 top crasher, #20 top startup crasher.
Reporter | ||
Updated•8 years ago
|
status-firefox48:
--- → affected
status-firefox50:
affected → ---
Comment 1•8 years ago
|
||
Similar to bug 1034706?
Comment 2•8 years ago
|
||
(In reply to Sylvestre Ledru [:sylvestre] from comment #1)
> Similar to bug 1034706?
Somewhat, though this one is almost perfectly correlated with a single CPU model (~98% AuthenticAMD family 16 model 6 stepping 3 | 2), whereas the other one is concentrated across several AMD CPU models.
Comment 3•8 years ago
|
||
Crash volume for signature 'js::FrameIter::functionDisplayAtom':
- nightly(version 50):0 crashes from 2016-06-06.
- aurora (version 49):0 crashes from 2016-06-07.
- beta (version 48):624 crashes from 2016-06-06.
- release(version 47):41 crashes from 2016-05-31.
- esr (version 45):6 crashes from 2016-04-07.
Crash volume on the last weeks:
W. N-1 W. N-2 W. N-3 W. N-4 W. N-5 W. N-6 W. N-7
- nightly 0 0 0 0 0 0 0
- aurora 0 0 0 0 0 0 0
- beta 557 1 3 2 2 3 0
- release 2 6 1 8 4 10 6
- esr 2 0 0 1 1 1 1
Affected platform: Windows
status-firefox47:
--- → affected
status-firefox-esr45:
--- → affected
Updated•8 years ago
|
Updated•7 years ago
|
Keywords: triage-deferred
Priority: -- → P3
Comment 4•7 years ago
|
||
This signature isn't showing up in any meaningful way anymore. The crashes no longer show any CPU model correlation.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
Updated•3 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•