3 ms·
WebGL implementations zero out newly allocated buffers for exactly that reason. https://www.khronos.org/registry/webgl/specs/latest/1.0/#4 https://www.khronos.
by hiker 11y ago
WebGL implementations zero out newly allocated buffers for exactly that reason.
https://www.khronos.org/registry/webgl/specs/latest/1.0/#4 https://www.khronos.org/registry/webgl/specs/latest/1.0/#4
- TheLoneWolfling 11y agoHow long until we get a heartbleed-like attack where some software overruns its GPU buffer into a webgl buffer?
- MaulingMonkey 11y agoFWIW I've been running with WebGL disabled because of similar concerns.
- thrownaway2424 11y agoWebGL works if you enable it? On Linux I've never seen anything other than error messages from WebGL.
- thristian 11y agoWebGL exercises some new corners of the OpenGL interface that many drivers weren't prepared for when WebGL arrived, so browsers tend to have an extensive blacklist: if you have a driver on the list, you won't get WebGL. On a rolling release like Debian Testing, with well-supported hardware like the Intel Ivy Bridge integrated GPU, WebGL has always worked beautifully.
- gkop 11y agoYou can try overriding the blacklist in Chrome, that worked well for me when I needed to for a Debian/Nvidia system a couple years ago.
- MaulingMonkey 11y agoAhh, I've been disabling it on Windows, however silly that might be.