Crashes at gpusGenerateCrashLog with graphics kernel error '0xfffffff9/-7'
Categories
(Core :: Graphics, defect)
Tracking
()
People
(Reporter: smichaud, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: topcrash, topcrash-startup)
Crash Data
As of bug 1577886, Socorro is now recording crashes with mac_crash_info
. This bug is to keep track of crashes whose signatures contain "gpusGenerateCrashLog" and whose "graphics kernel error" is '0xfffffff9/-7'.
They are almost certainly caused by one or more Apple bugs. There may not be anything Mozilla can do about them, beyond keeping track of them.
The "graphics kernel error" '0xfffffff9/-7' is defined in the /System/Library/Extensions/IOAcceleratorFamily2
kernel-mode graphics driver (where it's considered a "context error"). It means something like "out of memory".
I reported a fix for one of these bugs to Apple (see bug 1576767 comment 295), which they seem to have implemented in macOS 11.1 (see bug 1576767 comment 342). But it appears others remain unfixed. Or maybe new ones have been introduced.
At least so far, all of these crashes are on AMD Radeon hardware using the AMDRadeonX4000 hardware-specific kernel-mode graphics driver, and on macOS 11.3.1.
Recent examples:
bp-c6c0875e-2087-419f-a741-4292a0210518
bp-ba16e882-24b8-4015-b599-52de00210517
bp-8db599be-08d4-4e0a-89c9-7610b0210517
bp-8ea2b48b-44ed-4735-9c8a-cea690210517
Reporter | ||
Updated•3 years ago
|
Reporter | ||
Updated•3 years ago
|
Reporter | ||
Comment 1•3 years ago
|
||
The "available physical memory" in all of comment #0's crash reports except one is quite large. This is not a conventional OOM bug.
Reporter | ||
Updated•3 years ago
|
Reporter | ||
Comment 2•3 years ago
|
||
Reporter | ||
Updated•3 years ago
|
Reporter | ||
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Comment 3•2 years ago
|
||
Closing because no crashes reported for 12 weeks.
Reporter | ||
Comment 4•2 years ago
|
||
These are still happening, and under the same signature(s). But for some reason the signature(s) are being recorded differently:
Comment 5•2 years ago
|
||
The bug is linked to a topcrash signature, which matches the following criterion:
- Top 5 desktop browser crashes on Mac on release (startup)
:bhood, could you consider increasing the severity of this top-crash bug?
For more information, please visit auto_nag documentation.
Reporter | ||
Comment 6•2 years ago
|
||
These crashes aren't happening in large numbers. To measure them accurately you need to search on mac crash info (as per comment #4 and as follows). There are serious disadvantages relying entirely on signatures to track bugs.
Updated•2 years ago
|
Comment 7•2 years ago
|
||
Based on the topcrash criteria, the crash signatures linked to this bug are not in the topcrash signatures anymore.
For more information, please visit auto_nag documentation.
Comment 8•1 year ago
|
||
Sorry for removing the keyword earlier but there is a recent change in the ranking, so the bug is again linked to a topcrash signature, which matches the following criteria:
- Top 20 desktop browser crashes on release (startup)
- Top 5 desktop browser crashes on Mac on release (startup)
For more information, please visit BugBot documentation.
Description
•