Indeed per the upstream discussion there *might* be things that can be improved in mutter to reduce this problem. But at the same time it is somewhat expected behaviour. Only unexpected above some unknowable threshold of CPU usage that is system-dependent.
So this bug is not invalid, but also not definitely valid, currently "Opinion".
Indeed per the upstream discussion there *might* be things that can be improved in mutter to reduce this problem. But at the same time it is somewhat expected behaviour. Only unexpected above some unknowable threshold of CPU usage that is system-dependent.
So this bug is not invalid, but also not definitely valid, currently "Opinion".