Maxim Solovyov
Maxim Solovyov
we use the x damage extension to know what parts of the screen have changed. however, it's mostly up to an application to report the damage. for example, xterm reports...
afaiu the rule you written is a guess and wrong. do `xprop | grep -i class` on the netflix window and write a proper rule.
closing as stale.
the xrender backend is slow by itself. it should be gpu-accelerated but it's still quite heavy on the cpu. there are optimization possibilities but this is not in the priority....
there's no known resource leaks in picom built from the latest commit in the `next` branch and A LOT was fixed since v10.2.
@l4desu-mizu, every shiny button github provides is a trap
superseded by cb6993f5a0592af95007df3c458cfa6073ed5bde and a8ef63dbc7543d2951c1a204732f1fe9189aa93c. thanks for bringing this to our attention!
does my [`always-rebind-pixmap`](https://github.com/absolutelynothelix/picom/tree/always-rebind-pixmap) branch with `PICOM_DEBUG=always_rebind_pixmap` fix the issue? i'm especially interested in testing it with the `d3d12` driver.
i guess the exact look of stuttering will be helpful in understanding the origin of the issue and debugging it, so would be good if you can capture it using...
i think we can just consider `GL_CONTEXT_LOST` a reason for a device reset