Daniel Csillag

> In fact all of the issues I was experiencing on pijuilio's fork are gone. No buggy workspace transitions where the window on the last workspace is still visible, I...

Compared to what?

> The performance issues got better with ev_timer_set(&ps->animation_timer, 1000, 0); // yes, an absurdly high number, but still not acceptable for me. When you tell me how to run a...

Whoaa, that's troubling. Thanks for looking into it. Your hypothesis about these being leaked textures makes some sense; if I remember properly, picom (without my code) stores a single texture...

There are no workspace switching animations on this fork. Are you sure you cloned the right repository? Or, perhaps, could you describe what you mean by "workspace switching animations"?

Do you have animation clamping enabled?

I've just checked, and it appears that the default is `animation-clamping = true`. Could you try disabling it (i.e., `animation-clamping = false`)? How much does that (disabling) help with performance?

Try disabling shadows as well?

Another thing I'd love to know is how many windows picom is trying to animate per frame. But I need to think a bit on how to measure this without...

Update: The main bottleneck appears to be the `bind_pixmap` call in `default_backend_render_shadow`. Which is weird, and I don't think should be the case. ~~Possibly related, I've noticed that when shadows...