• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

NVidia driver bug makes users see blue.

Twirlywoos said:
PhysXXX
Click to expand...

Hahhahaha best post on these forums for years.....

--------------

At the main subject, who cares.. Lol. Sky Broadband asks their new users to opt in if they want to see rated content since 1/1.

I believe we have been pushed to conservatism to the extreme nowadays, and mainly by those who were in their 20-30s during the 60s & 70s......... (I believe many you understand what I am talking about).
 
D.P. said:
It is up to the existing application to clear memory that is no longer needs if it thinks there is a security issue, most applications wont. The next application that gets the memory is responsible for clearing the allocated memory if it wants to but, 99% of the time you really don't need to.
Click to expand...


But when that application sole purpose it to let you browse the web with no records being kept, don't you think it would be a good idea to take the extra time to clear the bleeding memory you've just used to store that info.
 
Some people take things too seriously.:D

If anyone is worried about err fine art suddenly appearing on their screen, then don't view fine art or switch away from chrome.

I have finally found something to like about Microsoft Edge.:D:)
 
bru said:
But when that application sole purpose it to let you browse the web with no records being kept, don't you think it would be a good idea to take the extra time to clear the bleeding memory you've just used to store that info.
Click to expand...

Yes, and that is the responsibility of Google not nvidia.
 
I'd have thought the onus on chrome to clear the memory. Perhaps not with normal browsing, but when using incognito maybe it should take that wee bit longer to close down to clear up after itself.
 
Rroff said:
^^ I doubt it is any different on AMD, maybe happen a bit differently depending on how the drivers are written, etc. but as D.P. says its a normal programming practise.
Click to expand...


I'd rather give up porn anyways than switch to AMD



If I were a man who indulged in such things, that is! :D
 
Arguably there are two bugs here, but neither of them are in the NVidia Drivers.

- Chrome Incognito should be disposing of any memory it has used to prevent the possibility of other processes reading/displaying it (unintentionally in this case, but it would be easy exploit maliciously)

- Diablo shouldn't be displaying an uninitialized buffer - even if this means just initializing it to be black.
 
It's a video driver/operating system issue. If an application crashes then measures taken by said application to fuzz the display buffer are rendered useless. Therefore the display framework must handle it in the event the application does not.

So either Microsoft or Nvidia needs to fix it.
 
Armageus said:
Arguably there are two bugs here, but neither of them are in the NVidia Drivers.

- Chrome Incognito should be disposing of any memory it has used to prevent the possibility of other processes reading/displaying it (unintentionally in this case, but it would be easy exploit maliciously)

- Diablo shouldn't be displaying an uninitialized buffer - even if this means just initializing it to be black.
Click to expand...

Bingo
 
yashiro said:
It's a video driver/operating system issue. If an application crashes then measures taken by said application to fuzz the display buffer are rendered useless. Therefore the display framework must handle it in the event the application does not.

So either Microsoft or Nvidia needs to fix it.
Click to expand...

That isn't how operating system and drivers work. You ask the OS for memory
you get that memory and whatever was there when it was last used.



If an application crashed then there is a bug in that application, the OS or driver is not responsible for cleaning memory of a crashed application. That has been the fundamentals of OSs for the last 30 or more years!
 
D.P. said:
That isn't how operating system and drivers work. You ask the OS for memory
you get that memory and whatever was there when it was last used.



If an application crashed then there is a bug in that application, the OS or driver is not responsible for cleaning memory of a crashed application. That has been the fundamentals of OSs for the last 30 or more years!
Click to expand...

Agree with D.P.
 
D.P. said:
If the application doesn't clear the buffer then it is not a d river bug but a problem with the application.
Click to expand...

Where did I mention it was a driver bug? You were arguing semantics to which I replied that any unwanted or unexpected results that occur in software is a by definition a bug.
 
Update at 12:12 p.m. Pacific: Some Reddit users are reporting this issue also occurs with AMD graphics cards, adding to the validity that this is an OS X issue not an Nvidia one.
Click to expand...

So definitely not NVidia's fault then.
 
You must log in or register to reply here.
Back
Top Bottom