You are not logged in.
On a fresh Arch install, I experience a strange behavior: switching to a chrome window and sending any UI actions (like Ctrl+T for new tab) often has a noticeable lag (of about 500-1200ms, roughly, by guess).
It does not always happen but is easily reproducable, and it only happens if I have more Chrome windows open with separate user profiles. (I use many profiles for work, plus a personal, etc). Having only a single Chrome window open, I never experience this problem.
I'm using Wayland, an Intel GPU (meteor lake), Chrome package is google-chrome 131.0.6778.85-1 and I see no errors in journalctl or the chrome debug log which I enabled from the terminal temporarily. I have no suspicious extensions either, and I disabled the Chrome memory saver (as it really feeling like it's swapping back data from somewhere when that happens).
Any ideas how to hunt this issue down? Anyone else can reproduce this with multiple open profile windows?
Last edited by kjozsa (2024-12-03 17:11:10)
Offline
To add to this, I found several references of Chrome issues on Wayland, so I think that might be the root of this issue. Experimenting with Chrome settings, it seems that enabling "Wayland text-input-v3" at about://flags seems to improve the situation somewhat.. If it comes back, I might just fall back to Xorg though.
Last edited by kjozsa (2024-12-04 10:01:14)
Offline