Bugzilla

I've learned how to emulate this bug's crashes, including the "Graphics kernel error: 0xfffffff9" error string. From this I've learned that the error happens without any of the methods in the call stack doing an error return. All that's needed is that the "context error" be non-zero, in the AMDRadeonX4000 or AppleIntelHD5000Graphics kernel extensions, before either calls IOAcceleratorFamily2's equivalent of libGPUSupportMercury.dylib's gpusSubmitDataBuffers. Whatever I set the user-mode reflection of the "context error" to, that's what appears in the "Graphics kernel error" string.

I've still got a lot of work to do, though. I still need to figure out why the "context error" is being set in this way. And then I need to figure out what Firefox can do about it.

I've learned how to emulate this bug's crashes, including the "Graphics kernel error: 0xfffffff9" error string. From this I've learned that the crashes happen without any of the methods in the call stack doing an error return. All that's needed is that the "context error" be non-zero, in the AMDRadeonX4000 or AppleIntelHD5000Graphics kernel extensions, before either calls IOAcceleratorFamily2's equivalent of libGPUSupportMercury.dylib's gpusSubmitDataBuffers. Whatever I set the user-mode reflection of the "context error" to, that's what appears in the "Graphics kernel error" string.

I've still got a lot of work to do, though. I still need to figure out why the "context error" is being set in this way. And then I need to figure out what Firefox can do about it.