http://www.fudzilla.com/news/graphics/39631-nvidia-breaches-the-walls-of-chrome
Thank goodness I don't use Chrome.
Last edited:
-
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.
- Thread starter Kaapstad
- Start date
http://www.fudzilla.com/news/graphics/39631-nvidia-breaches-the-walls-of-chrome
Thank goodness I don't use Chrome.
Permabanned
- Joined
- 8 Jan 2010
- Posts
- 10,263
- Location
- UK
PhysXXX
Thank goodness I don't use Chrome.
Its not a bug really. In a programming language like C++ if you ask for a block of memory you get a block of memory with the contents of whatever was there before still entirely intact. that is just how operating systems work. When the program and then OS frees memory it doesn't overwrite it blank it out, that takes time and is pointless, you just get the random left overs of whatever used the memory before.
Soldato
- Joined
- 25 Nov 2011
- Posts
- 20,679
- Location
- The KOP
Ouch that is very bad hopefully they fix fast. I use chrome hope amd don't have issue.
Anything that happens in software when it clearly isn't meant to is a bug.
If the application doesn't clear the buffer then it is not a d river bug but a problem with the application.
As D.P. said its not really a bug as such - there are performance penalties with clearing bulk areas of memory and the normal programming practise is to clear a block before you use it - I'm not overly familiar with some of the mechanics but I thought there was as way to flag i.e. buffers for texture data to be dealt with by the driver's garbage collection i.e. so that it gets cleared, not just marked as free, if the application crashes without freeing data.
So switch to AMD or give up porn is the solution?
Unlucky fella's
^^ 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.
Nvidia damage control....
Or the actual truth that is supported by people that actually program.
What would be a big is if the memory was automatically cleared, that would be an obvious performance bug. This is entirely normal behavior, i encounter it all the time, even with openGL. there is a reason that the openGL API has this useful function:
glClearBuffer
https://www.opengl.org/sdk/docs/man/html/glClearBuffer.xhtml
If you don't clear a memory buffer then you will get whatever random memory was there, which doesn't matter because you are going to overwrite all that memory yourself.
*Disclaimer This post is not NVidia damage control but will be seen as such*
Sorry for being reasonably ignorant in the way that things are coded, but let me see if I have got this straight.
You intend to browse to a site using chrome, but you dot want anyone to know, so you use incognito mode.
Google chromes incognito mode help page states.
Well as far as you are concerned there is no record of you viewing, whatever you used incognito mode for, as Chrome says it doesn't keep track of it
Suddenly this info pops up in a game because the next programme to use the same memory space has access to the data, which isn't suppose to be recorded.
Just how it that NVidia's fault, chrome should have emptied that block of memory as it exited incognito mode.
If a bug in NVidia's driver can be blamed what about when the next piece of software, maybe some children's story book or something suddenly reads that area of memory, would that still be NVidia's fault, of course not. This is clearly Chromes fault for not clearing the data, which by its own statement isn't suppose to be kept track of anyway.
Yes there is obviously a bug in NVidia's driver that doesn't check the content of said memory block, but it cannot be held responsible for that info being there in the first place.
Sorry for being reasonably ignorant in the way that things are coded, but let me see if I have got this straight.
You intend to browse to a site using chrome, but you dot want anyone to know, so you use incognito mode.
Google chromes incognito mode help page states.
Well as far as you are concerned there is no record of you viewing, whatever you used incognito mode for, as Chrome says it doesn't keep track of it
Suddenly this info pops up in a game because the next programme to use the same memory space has access to the data, which isn't suppose to be recorded.
Just how it that NVidia's fault, chrome should have emptied that block of memory as it exited incognito mode.
If a bug in NVidia's driver can be blamed what about when the next piece of software, maybe some children's story book or something suddenly reads that area of memory, would that still be NVidia's fault, of course not. This is clearly Chromes fault for not clearing the data, which by its own statement isn't suppose to be kept track of anyway.
Yes there is obviously a bug in NVidia's driver that doesn't check the content of said memory block, but it cannot be held responsible for that info being there in the first place.
Last edited:
nvidia's driver is not supposed to check the contents of a memory block, the driver just provides a region of memory that is not being used by anything. 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.