Bugzilla

Very interesting that your "graphics kernel error" changed -- it was 0xfffffff9/-7 and is now 0xfffffffc/-4. Grepping through the IOAccelerator2Family kernel extensions's assembly code, the new error code seems to mean "stream error". Your crash took the same path through gpusSubmitDataBuffers(), though -- the path not effected by `no_crash_upon_reset`.

Do you have two Apple crash reports (one for each crash)? If so, please also attach the other one.

In my experience, dtrace is only really useful when you start digging through assembly code, and begin to understand how it works. It helps you solidify your understanding, and cut off false trails (for example because a method you're interested in never gets called). The same is true of HookCase.

You didn't see any wakeup logs for Firefox. I assume you also didn't see "Slow WS Update data" ones. If so my "window server congestion" idea is definitely a red herring.

Now that I have another "graphics kernel error", I'll need to widen my search for kernel extension code to "tickle", in my attempt to find out how these crashes happen.

Very interesting that your "graphics kernel error" changed -- it was 0xfffffff9/-7 and is now 0xfffffffc/-4. Grepping through the IOAcceleratorFamily2 kernel extensions's assembly code, the new error code seems to mean "stream error". Your crash took the same path through gpusSubmitDataBuffers(), though -- the path not effected by `no_crash_upon_reset`.

Do you have two Apple crash reports (one for each crash)? If so, please also attach the other one.

In my experience, dtrace is only really useful when you start digging through assembly code, and begin to understand how it works. It helps you solidify your understanding, and cut off false trails (for example because a method you're interested in never gets called). The same is true of HookCase.

You didn't see any wakeup logs for Firefox. I assume you also didn't see "Slow WS Update data" ones. If so my "window server congestion" idea is definitely a red herring.

Now that I have another "graphics kernel error", I'll need to widen my search for kernel extension code to "tickle", in my attempt to find out how these crashes happen.