-
-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Workspace Switching Becomes Slower Over Time #209
Comments
You can capture the log with |
Letting Sometimes typing freezes. But the mouse pointer freezes equally as much and for as long. Every 30 seconds or so it can be quote pronounced (maybe 100ms+ or so - long enough for me to think "that's annoying"). So it's not limited to the keyboard. I think these messages could be an artifact in something else. Some kind of lower level event processing problem. Is there a mailing list or forum for Xwayland? What's the next level down in the event stack? Of course this is probably multiple overlapping problems maybe interacting with one another. Any one issue people probably don't notice or bother to complain. But when combined they are annoying and difficult to debug.
|
Are you sure this is related to this extension? Also, you can always try out xorg to see if it's really a wayland problem. |
Please reopen if you have new information regarding this issue. |
When first logging in, workspace switching is reasonably quick (<100ms maybe). But after about a week, workspace switching becomes noticeably slower. After two weeks it starts to become so slow (500ms+) that I have to log out and back in.
I'm trying to figure out if it's Xwayland, the gnome shell or gnome-shell-wsmatrix. How does one log gnome-shell events? Is there something to enable logging to systemd?
If I run xev, and, as quickly as I can, press Ctrl-Alt-Up, Down, Up, Down without waiting for any switching, I get the following
Converting timestamps to S.ms I see:
So I depress Ctrl-Alt, pause for 2 seconds and then the press up arrow triggers some events. Then xev is off screen so it doesn't capture the down arrow. But 246 ms later it does capture the second up arrow. Doing this two other times I get 235 ms and 242 ms.
Note1: I complete the up-down-up-down sequence long before the workspaces even start to switch. So I do up-down-up-down, then there's a seemingly 500ms+ delay and then the workspace switches, pauses very briefly (to display the gnome-shell-wsmatrix popup) and then switches back to the previous workspace.
Note2: Even though I did up-down twice, the workspace appears to only switch up and down once.
Gnome in general can be a little "sticky". The mouse can freeze momentarily for a few hundred ms. Scrolling with mouse wheel in FF can stick briefly. Typing sometimes freezes for a couple hundred ms. As a software developer myself who has written low-level code like drivers and such, my guess would be that there's some bloat somewhere. The hardest problems are always multiple overlapping problems. The first step to figuring this out is going to be to capture timestamps and see were the delay shows up. So how can I capture timestamps from gnome shell?
Using Fedora 41 on newish Dell Latitude laptop. Animations are off. Static Workspaces. I believe I also changed something about how long the "popup" is displayed but I don't recall what setting was used (where?).
Running very few apps. Just FF, claws mail and 6 separate gnome-terminals.
I am not experiencing the level of problems described in issue #190. However, I would like to know how that user is capturing log information.
The text was updated successfully, but these errors were encountered: