In the spirit of some live conversations and https://bugzilla.mozilla.org/show_bug.cgi?id=1189940#c40, we may want to extend the blocklisting mechanism to be smarter. We "blocklist" the driver/version combination if we experience a startup crash. We can also blocklist particular hardware/driver combinations wholesale. What we may want to do is add blocklisted hardware/driver combinations that actively blocklist only if the user has experienced (frequent? certain number?) crashes that point to certain signatures. This probably fits under the larger "runtime hardware testing" umbrella, as effectively we're adding the concept of non-startup crashes effecting the settings, but also potentially a soft-block list from which to select from.

The crash reporter may be the place where some of this works gets done and soft-block lists get looked at...

> What we may want to do is add blocklisted hardware/driver > combinations that actively blocklist only if the user has experienced > (frequent? certain number?) crashes that point to certain signatures. Getting "proper" signatures would be a large effort. We don't have that information locally, so you'd need to get the crash processed by crash-stats and ask what signature you got. As an approximation, you might want to just look at which DLL you crashed in, and see if it's a known graphics library or driver.

The DLL is probably good enough. If you're on a "at risk" hardware/driver combo and we see a lot of driver DLL crashes, we do something, probably with some user interaction.