Yuxuan Shui
Yuxuan Shui
Could be a bug of `use-damage = true`. Does the problem go away if you disable that?
That's odd as you are not even using the xrender backend
Hmm, can't reproduce that. Can you try build with address sanitizer?
Thanks. But you want to use `--buildtype=debug`, otherwise the stack trace won't be very useful.
Thanks for the report! It has been fixed in the `next` branch. Although this is probably not related to the original bug.
Can you [grab a trace](https://github.com/yshui/picom/wiki/Reporting-issues#capture-a-trace), with the glx backend?
From your trace it looks like the bright/"overexposed" window comes straight from kitty itself. picom is rendering that window correctly. maybe kitty is doing something weird?
When you say this starts to happen after ffb8bc5b29c3cf40cdb5578886d11dcbfd59a74e, did you mean you did a git bisect? If you didn't, can you please do that?
Does this happen outside of VMware too? Can you try running picom on host side if you were able to.
I am thinking this could be a VMware driver issue. Would be nice if we could find out if this happens outside VMware. Just by looking at the GLSL change...