Great to hear. But please don't use dragging windows as a CPU test. Even without this bug (e.g. Intel GPUs) dragging windows is very heavy on the CPU. That's a separate bug (not yet reported upstream?). The fixes required for high CPU usage when dragging windows are:
And I don't think we need to worry about __GL_MaxFramesAllowed=1. That's what mr281 does.
---
Hussam,
I'm very glad you find those patches work and I would like mutter to get both. But for this bug I think it's work pointing out you only need mr363. Once you have that this bug is fixed, and adding mr281 only reduces output latency (which is nice, but not relevant here).
Maik,
Great to hear. But please don't use dragging windows as a CPU test. Even without this bug (e.g. Intel GPUs) dragging windows is very heavy on the CPU. That's a separate bug (not yet reported upstream?). The fixes required for high CPU usage when dragging windows are:
* Closure of https:/ /gitlab. gnome.org/ GNOME/mutter/ issues/ 283 and /gitlab. gnome.org/ GNOME/mutter/ merge_requests/ 270 but better.
* Something like https:/
And I don't think we need to worry about __GL_MaxFramesA llowed= 1. That's what mr281 does.
---
Hussam,
I'm very glad you find those patches work and I would like mutter to get both. But for this bug I think it's work pointing out you only need mr363. Once you have that this bug is fixed, and adding mr281 only reduces output latency (which is nice, but not relevant here).