On dual-GPU machines on Windows, we currently listed both GPUs in about:support but only blacklist based on the first GPU. This is a problem when it turns out we're actually using GPU #2, or when we end up switching from GPU #1 to GPU #2 (as in Bug 635464). We should consider blacklisting based on both GPUs -- that is, blacklist if either of the GPUs has a blacklisted driver. Before doing this, we should look at crash report data (starting with Firefox 11, where dual-GPU detection was cleaned up by Bug 679110) and the telemetry data added by Bug 706340 to estimate the percentage of users who would be affected by this change.
Likely a dupe of bug 628129 ?
(In reply to Paul Irish from comment #1) > Likely a dupe of bug 628129 ? Not a dupe, since this bug for doing something blunter than Bug 628129: this bug is for blacklisting when either of the drivers is blacklisted, while Bug 628129 is for figuring out which GPU is active and then blacklisting if the active GPU's driver is blacklisted.
Assume you got a machine with an integrated GPU and a dedicated GPU. Then the dedicated GPU gets blacklisted, for whatever reason. The driver-configuration of the dedicated GPU is set to never switch from the integrated GPU to the dedicated GPU, so the problem of the dedicated GPU never affects the browser. Why should the browser also stop using HWA for the unaffected GPU?
You need to log in before you can comment on or make changes to this bug.