11–20 of 77 posts
The proper solution, of course, i for GPU drivers not to suck but it was still a legitimate point and this article seems to validate that.
Earlier quoted context omitted.
Yeah - that sounds like fun - recreating a driver install issue after you finally have it working on your system. Heck, even if you set up a system -just- to recreate this problem, it would still be one of those "nightmare inducing" trials of will. I'm not saying it shouldn't be done, I just can't imagine doing it (especially on my personal workstation).
Plus you paid for the computer, graphic card and OS. Why in hell would you spend hours of work on your free time for this ? Do people try to find defects in their car then send a report to Ferrari ?
Yes.
-- Ferruccio Lamborghini.
A lot of people hated the decision, but back when Microsoft refused to support WebGL, one of the reasons were that the GPU drivers were awful and exposing them to the internet was dangerous. The proper solution, of course, i for GPU drivers not to suck but it was still a legitimate point and this article seems to validate that.
A lot of people hated the decision, but back when Microsoft refused to support WebGL, one of the reasons were that the GPU drivers were awful and exposing them to the internet was dangerous. The proper solution, of course, i for GPU drivers not to suck but it was still a legitimate point and this article seems to validate that.
Earlier quoted context omitted.
Oh trust me, they do tons of QA. If you can replicate what problem you have demonstrably with steps that QA can follow and you submit to the Nvforums or whatever, someone in the QA team will eventually try it out.
I dunno, I have had to live with this bug ( https://forums.geforce.com/default/topic/953432/geforce-mobi... , https://answers.microsoft.com/en-us/windows/forum/windows_10... ) for over half a year now.
I wonder if AMD drivers have the same attack surfaces as the nvidia drivers Edit: a quick google search turns up CVEs for the old catalyst driver, but none for the newer crimson drivers.
A lot of people hated the decision, but back when Microsoft refused to support WebGL, one of the reasons were that the GPU drivers were awful and exposing them to the internet was dangerous. The proper solution, of course, i for GPU drivers not to suck but it was still a legitimate point and this article seems to validate that.
The post specifically mentions that these things are not vulnerable to attack from WebGL, because you can't reach the APIs in question just by drawing.
I cant prove this but my computer blue screened after a Nvidia driver update. It took my several hours to get everything working again because it wouldnt even launch in safe mode. Very frustrating. I wish they had a little more quality control on their drivers.
Oh trust me, they do tons of QA. If you can replicate what problem you have demonstrably with steps that QA can follow and you submit to the Nvforums or whatever, someone in the QA team will eventually try it out.
Wasn't too terribly impressed with the team (and a couple of them were definitely giving off that "I hate my job/life" vibe, one disgruntled fellow was even trying to drop little thinly-veiled "run away!" hints at me). I figure either the cream of the crop at Nvidia doesn't work in QA, or they don't get proper support from upper management.
P.S. Didn't get an offer anyway, probably for the best - I was desperate for work at the time and would have taken it :)
A lot of people hated the decision, but back when Microsoft refused to support WebGL, one of the reasons were that the GPU drivers were awful and exposing them to the internet was dangerous. The proper solution, of course, i for GPU drivers not to suck but it was still a legitimate point and this article seems to validate that.
Whereas Chrome implemented a WebGL compiler that reduced the amount of attack surface WebGL could reach and audited a bunch of popular drivers to fix the exposed bits.
I think the fact that this blog shows that these vulnerabilities are not reachable from WebGL is a validation of Chrome's approach there, though it clearly shows the issues these drivers present for escaping Chrome's sandbox.