Comment by ~eliasnaur on ~eliasnaur/gio
Unfortunate. Can you try the amended commit? I've tightened the glFlush to a glFinish.
Comment by ~eliasnaur on ~eliasnaur/gio
Can you try the workaround I pushed to the "ci" branch, https://gioui.org/commit/867329f53fd63b59467bcf82edc266112c8844b5? It fixes the issues on my Pixel 1.
on ~eliasnaur/gio
REPORTED RESOLVED IMPLEMENTED
Comment by ~eliasnaur on ~eliasnaur/gio
Is this still reproducible with the newest version of Gio? If so, can you tell me the DPI and viewport size of your devices?
Comment by ~eliasnaur on ~eliasnaur/gio
Change https://gioui.org/commit/b87cbc04f37453a064201a8590b0a23a169cf3f5 also fixes the 0x502 issue for me on pop! OS. Marking this fixed.
REPORTED RESOLVED FIXED
Comment by ~eliasnaur on ~eliasnaur/gio
Hm, I spoke too soon. The https://gioui.org/commit/b87cbc04f37453a064201a8590b0a23a169cf3f5 change fixes the hang for me, which indicates that the command stream to the compute programs before the change was sometimes incorrect. This is quite likely, so I'm going to close this issue for now and concentrate on #214 (NVIDIA), #221 (font glitches) and issues on my own Pixel 1 phone.
REPORTED RESOLVED FIXED
Comment by ~eliasnaur on ~eliasnaur/gio
Turns out I'm the idiot: by adding "GIORENDERER=forcecompute" (and spelling it correctly) I can easily reproduce the hang. Sorry for putting you on a wild goose chase.
FWIW, there has been no change to the compute shaders from 4f40b58e0d14..8cec7e04eb71 so if the issue is gone at your end it probably means caching is somehow hiding the issue.
Comment by ~eliasnaur on ~eliasnaur/gio
No luck on GNOME.
Comment by ~eliasnaur on ~eliasnaur/gio
Thank you for the simple reproducer. Unfortunately it doesn't hang for me. I'm running Sway on Fedora 34. Is there a chance you can reproduce the hang on F34?
Comment by ~eliasnaur on ~eliasnaur/gio
There is no longer a hard requirement on GPU sRGB support.
REPORTED RESOLVED FIXED