CHIPMAKER Nvidia has denied that it's to blame for a bug that caused Google Chrome's private browsing Incognito mode to fail.
We reported on the so-called GPU bug on Tuesday, after a blogger named Charliehorse55 claimed to discover that users of Google Chrome with Nvidia graphics chips don't always get Incognito mode, even when the machine says it's on.
He explained that after a furious session of ... um ... present buying, he decided to play Diablo III and was confronted, not with the loading screen, but an unloading screen showing all of the ... um ... presents.
The blame was placed firmly on Nvidia, with the blogger moaning that Nvidia GPUs don't flush the memory buffer at the end of a browsing session, and neither does Google Chrome, so even if you've been very careful to use Incognito mode, your dinkle pics may well come back to haunt you, because they can't be deleted. In fact, you can't rub one out. Not one.
Charliehorse55 said in his blog: "This is a serious problem. It breaks the operating system’s user boundaries by allowing non-root users to spy on each other. Additionally, it doesn’t need to be specifically exploited to harm users - it can happen purely by accident.
"Anyone using a shared computer could be exposing anything displayed on their screen to other users of the computer."
After earlier acknowledging the problem, Nvidia has seemingly realised that it's not at fault, and told The INQUIRER in a statement that the problem in fact lies in Apple's Mac OS X software.
In a statement sent to The INQUIRER, a Nvidia spokesperson said: "This issue is related to memory management in the Apple OS, not NVIDIA graphics drivers.
"The NVIDIA driver adheres to policies set by the operating system and our driver is working as expected.
"We have not seen this issue on Windows, where all application-specific data is cleared before memory is released to other applications."
Apple, naturally, has yet to comment. µ
Apple accused of weaponising the App Store to favour Apple Music
Something else for carriers to blame poor reception on
Will it work on Songs for the Deaf?
What took so long?