Bug#943563: chromium crash when trying to check error status after invalidateing framebuffer in WebGL

2020-01-22 Thread Witold Baryluk
Package: chromium Followup-For: Bug #943563 Looks to be fixed in chromium 79. I can't reproduce it now on the same hardware, but with Mesa 19.3.2 (I was testing with Mesa 19.2.1 previously). In fact the framebuffer invalidation tests all pass now, and no crashes either. There are some other

Bug#943563: chromium crash when trying to check error status after invalidateing framebuffer in WebGL

2019-11-16 Thread Witold Baryluk
Package: chromium Version: 78.0.3904.97-1+b1 Followup-For: Bug #943563 Tested with newer chromium from unstable. This is with mesa from Debian testing and debug symbols enabled: Thread 20 "Chrome_InProcGp" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffb27fc700 (LWP

Bug#943563: chromium crash when trying to check error status after invalidateing framebuffer in WebGL

2019-11-08 Thread Michael Gilbert
control: tag -1 moreinfo On Sat, Oct 26, 2019 at 10:48 AM Witold Baryluk wrote: > Thread 20 "Chrome_InProcGp" received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0x7fffaa7fc700 (LWP 32634)] > 0x7fff770d9c37 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so > (gdb) bt

Bug#943563: chromium crash when trying to check error status after invalidateing framebuffer in WebGL

2019-10-26 Thread Witold Baryluk
Package: chromium Version: 76.0.3809.100-1 Severity: normal Dear Maintainer, When visiting https://www.khronos.org/registry/webgl/sdk/tests/conformance2/renderbuffers/invalidate-framebuffer.html?webglVersion=2=0=1 the test fails: This tests invalidateFramebuffer and invalidateSubFramebuffer