This bug was filed from the Socorro interface and is report bp-bd946405-b964-42aa-b669-c426f2160902. ============================================================= There are substantially more crashes with signature [@ sse2_blt] in 49.0b7 and 49.0b8 than there were in previous releases. See queries at https://crash-stats.mozilla.com/signature/?product=Firefox&date=%3E2016-05-01&signature=sse2_blt#aggregations They have somewhat similar hardware patterns as the crashes in bug 1296630, but different patterns in terms of which releases they're in.
Perhaps an even more precise query for the ones that regressed is: https://crash-stats.mozilla.com/search/?signature=~sse2_blt&address=%5E0xffffffffffff&date=%3E2016-06-01&product=Firefox&_sort=-date&_facets=signature&_facets=cpu_info&_facets=version&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform_pretty_version&_columns=app_notes&_columns=graphics_critical_error&_columns=address#facet-version They happen pretty much entirely on "GenuineIntel family 6 model 61 stepping 4" CPUs.
Didn't we enable SSE recently, which could explain these?
I now think it's more likely that this is the same problem as bug 1296630.
(In reply to Mason Chang [:mchang] from comment #2) > Didn't we enable SSE recently, which could explain these? What was it exactly that was enabled, and was it in the 49 cycle?
(Is bug 1296630 comment 55 what you meant?)
(In reply to David Baron :dbaron: ⌚️UTC-7 (busy September 14-25) from comment #5) > (Is bug 1296630 comment 55 what you meant?) Yup looks like it.
No longer a topcrash but still being reported, down 81% since peak in September: > 53.*: 0 reports in the last week > 52.*: 0 reports in the last week > 51.*: 18 reports in the last week > 50.*: 69 reports in the last week > 49.*: 2 reports in the last week
status-firefox49: affected → wontfix
status-firefox50: --- → affected
status-firefox51: --- → affected
You need to log in before you can comment on or make changes to this bug.