To view parent comment, click here.
To read all comments associated with this story, please click here.
Yep, indeed: with WebGL we are basically exposing 95% of the OpenGL API to random scripts from the Web. So even "innocuous" graphics driver bugs can suddenly become major security issues (e.g. leaking video memory to scripts would be a huge security flaw). Even a plain crash is considered a DOS vulnerability when scripts can trigger it at will. So yes, WebGL does put much stricter requirements on drivers than, say, video games or compiz.
But is it the job of Firefox to shield from blatant (security) bugs in the underlying OpenGL API and neglecting the bugfree implementations in the process?
Rather more use and exposure would motivate the driver developers to fix their buggy drivers.
Perhaps a blacklist could be implemented notifying the users that their driver is buggy and Firefox will run unaccelerated? This would raise awareness without negatively affecting the "good systems".
Edit: I see you have already implemented a blacklist :-) But perhaps still notifying the user would be a good idea?
Edited 2011-01-15 18:58 UTC
There's a major difference between both: if you use a sane (process oriented) design: a bug in an html(etc) component only crash a tab, or at worse the webbrowser (if poorly designed), a bug in an OpenGL driver can crash the *whole* computer and it is much, much more complex to debug, especially with hardware acceleration, and without hw acceleration OpenGL isn't very interesting!





Member since:
2009-06-30
Well, there is a chance they will.
Linux OpenGL implementations are not very different from what we (used to?) have with html+css+... implementations. They are a buggy, inconsistent mess but if you know the safe path across the minefield you can still produce a working product. Sometimes the obvious path is not the "proper" one.
It's likely that Mozilla guys are performing some operations that don't match the semantics of underlying layers well (after all it's a multiplatform program). Such corner cases are more likely to have bugs or suffer from poor performance. This of course is not an excuse for guys producing these bugs but I can easily imagine another application doing the same things differently and managing to work these bugs around.