This WebGL testcase just creates a huge blank texture and draws a quad with it: http://people.mozilla.org/~bjacob/webgltexture2D5k.html You should see only black. But here I occasionally see some corruption with vertical yellow stripes on a rectangular part of the image. Reloading the page a few times makes the problem go away. The testcase uses webgl.texImage2D with null pixel data, which causes the browser to calloc() a buffer and pass it to glTexImage2D. So it's not just an uninitialized texture. The application is doing what's right to properly initialize the texture with zero'd image data. If there is any risk that this might be exposing uninitialized texture memory, then please treat this as a high priority, as we'd have to find a work around. FWIW, on a different proprietary platform, this does expose video memory and forced us to artificially limit the max texture size to 4k.
By the way, this is on Ubuntu 11.10, 64 bit, X.Org -- Gallium 0.4 on AMD RV710 -- 2.1 Mesa 7.11
Can you try with a newer version of mesa?
Maybe, if there is a package for Ubuntu 11.10 that is safe and easy to install?
The safest way would be to just try a 12.04 beta 2 or newer livecd out, it has 8.0.2
FWIW, for me the test segfaults with 8.0 but works (without artefacts AFAICT) with 8.0.2. This is on a HD 5670. (I suppose the component of the bug should be moved to Drivers/Gallium/r600 ?)
(In reply to comment #0) > This WebGL testcase just creates a huge blank texture and draws a quad with it: > > http://people.mozilla.org/~bjacob/webgltexture2D5k.html > > You should see only black. But here I occasionally see some corruption with > vertical yellow stripes on a rectangular part of the image. Reloading the page > a few times makes the problem go away. > > The testcase uses webgl.texImage2D with null pixel data, which causes the > browser to calloc() a buffer and pass it to glTexImage2D. So it's not just an > uninitialized texture. The application is doing what's right to properly > initialize the texture with zero'd image data. > > If there is any risk that this might be exposing uninitialized texture memory, > then please treat this as a high priority, as we'd have to find a work around. > > FWIW, on a different proprietary platform, this does expose video memory and > forced us to artificially limit the max texture size to 4k. With current firefox nightly 20120808 and current mesa 8.1-devel (git-be42a45) this site works for me. I see only black. WebGL Renderer: X.Org -- Gallium 0.4 on AMD RV770 -- 2.1 Mesa 8.1-devel (git-be42a45) Feel free to reopen this report if the issue persists.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.