The gfx blocklist has proved its inefficiency to prevent crashes caused by bug 772330. The latest ones happened in 10.0.6esr. Cancel the Direct3D 9/DIRECT2D blocklist for this set of GPUs.
I need confirmation
Whoops, incomplete message. I need confirmation that we want to remove these blocks. Are we sure they didn't help at all?
a=me to remove the blocks, obviously with follow-up monitoring to make sure the crashes don't spike again.
I've deleted both blocks from staging. Juan, please verify that the blocks are gone from blocklist.xml and their removal works correctly.
Jorge: I have the machine at my desk for this testing. I modified about:config to point to staging and it appears as if it works correctly as now I am unblocked and I do not see those entries in blocklist.xml (would be helpful to reference the block IDs so it is easier to verify on the QA side). Graphics Adapter Description AMD Radeon HD 6310 Graphics Vendor ID 0x1002 Device ID 0x9802 Adapter RAM 384 Adapter Drivers aticfx64 aticfx64 aticfx64 aticfx32 aticfx32 aticfx32 atiumd64 atidxx64 atidxx64 atiumdag atidxx32 atidxx32 atiumdva atiumd6a atitmm64 Driver Version 8.982.0.0 Driver Date 7-27-2012 Direct2D Enabled true DirectWrite Enabled true (6.1.7601.17789) ClearType Parameters ClearType parameters not found WebGL Renderer Google Inc. -- ANGLE (AMD Radeon HD 6310 Graphics) -- OpenGL ES 2.0 (ANGLE 220.127.116.112) GPU Accelerated Windows 1/1 Direct3D 10 AzureCanvasBackend direct2d AzureFallbackCanvasBackend cairo AzureContentBackend direct2d
Looks good. I've removed the blocks from prod. Please make sure that blocks g81 and g95 are not in the blocklist anymore (it can take up to an hour for the blocklist to refresh server-side).