Nvidia GPUs can break Chrome's incognito mode

Re:Nvidia GPUs can break Chrome's incognito mode by CountSessine on Saturday January 09, 2016 @11:09PM (#10874104)

Across an entire computer system? For all applications? Even games? Sharing data across process boundaries is undesirable, but is something most computer users would accept if the alternative was reduced performance.

Why not just fix this in the browser? The real issue here is that this data isn't just being shared across processes but potentially with websites through malicious webgl.

[ Parent | on HN ]

Re:Nvidia GPUs can break Chrome's incognito mode by Dylan16807 on Saturday January 09, 2016 @11:19PM (#10874128)

If you can waste the time on allocating a buffer, you can waste the time on zeroing it. If you're in a hot loop you shouldn't be allocating giant chunks of memory.

[ Parent | on HN ]

Re:Nvidia GPUs can break Chrome's incognito mode by CountSessine on Saturday January 09, 2016 @11:42PM (#10874197)

It would be interesting to know how the cost of allocating a new fbo would compare to the cost of zeroing it out. My guess is that the cost of getting into the kernel to do the allocation in the first place would dominate, but by how much would be something neat to measure.

[ Parent | on HN ]

Re:Nvidia GPUs can break Chrome's incognito mode by chris_wot on Sunday January 10, 2016 @06:09AM (#10874948)

If it's costing a lot of time to clear a buffer, doesn't that tend to indicate that's something the video card manufacturer should design an enhancement or fix for?

[ Parent | on HN ]