Closed Bug 1160317 Opened 10 years ago Closed 9 years ago

crash in nsIFrame::StylePosition()

Categories

(Core :: Layout, defect)

39 Branch
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 772330
Tracking Status
firefox39 + wontfix

People

(Reporter: MatsPalmgren_bugz, Unassigned)

References

Details

(Keywords: crash, topcrash)

Crash Data

This bug was filed from the Socorro interface and is report bp-e06915e6-4bd5-4aee-b674-f63e02150428. ============================================================= This signature is spiking in 39a2, it's currently the #4 topcrash. All crashes are on Windows. I think this is a variation of the "AMD bug" (bug 772330). Reported crashes for the past 7 days: Product Version Percentage Number Of Crashes Firefox 39.0a2 98.28 % 400 Firefox 37.0.2 0.74 % 3 Firefox 40.0a1 0.49 % 2 Firefox 38.0a2 0.25 % 1 Firefox 39.0a1 0.25 % 1
[Tracking Requested - why for this release]: topcrash #4
Indeed. Rank Cpu info Count % 1 AuthenticAMD family 20 model 2 stepping 0 | 2 326 59.38 % 2 AuthenticAMD family 20 model 1 stepping 0 | 2 221 40.26 % 3 AuthenticAMD family 20 model 1 stepping 0 | 1 2 0.36 %
I'll track this for now, but given the evasiveness of the other AMD crashes this may not be actionable or may shimmer off into the sunset in the next build.
Jet is this something that your team will take a look at? The crash rate for this signature has dropped now, but it spiked on the 2015042800 build.
Flags: needinfo?(bugs)
(In reply to Liz Henry (:lizzard) from comment #4) > Jet is this something that your team will take a look at? Yes. See bug 772330 comment 49.
Flags: needinfo?(bugs)
I could still take a patch for this for beta 39. It doesn't look like there is any progress in bug 772330 though.
This is not currently an issue in 39, but it has spiked unpredictably in several versions over the last few years. So while we can take a fix it is not an immediate issue.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.