Firefox incompatible with nVIDIA Kepler GPU for over 5 years, why is hardware acceleration enabled with updates?
Long story short I have a few 650/660/670 nVIDIA cards and with hardware acceleration enabled Firefox crashes the GPU entirely causing a hardware watchdog to take over. Any reason why Firefox does not keep a repository of system hardware known to cause TDRs and system faults?
All Replies (4)
There is a list: https://wiki.mozilla.org/Blocklisting/Blocked_Graphics_Drivers
But we don't expect every GPU to be tested and known to work with Firefox or not. Someone has to file a bug to add GPU to the blocklist.
TyDraniu said
There is a list: https://wiki.mozilla.org/Blocklisting/Blocked_Graphics_Drivers But we don't expect every GPU to be tested and known to work with Firefox or not. Someone has to file a bug to add GPU to the blocklist.
The link you've brought is not functional. Trying to go to bugzilla with it defaults to a blank 'submit bug' page.
Windows 98SE has a feature to where if the computer goes non-responsive (and/or loses power) in suspend mode it will disable that feature on the fifth occurrence. If Firefox keeps hanging and not shutting down properly I'd imagine we'd be at a point where it would kick in and try to figure out what's failing. Of course I don't mind having to trial and error because Firefox also doesn't not know how to interact with an nForce board but 5 years is ridiculous.
Modified by Prismatic
I would say either one of those install is corrupted or bad install is more likely the cause of the problem.
WestEnd said
I would say either one of those install is corrupted or bad install is more likely the cause of the problem.
Freshly installed Windows on a secure erased SSD would be odd if a component had a 100% chance of corruption upon install, especially since I've been able to replicate this issue after many wipes.
That being said, when the GPU does crash it re-enables performance settings on Firefox.