-
Notifications
You must be signed in to change notification settings - Fork 936
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
random tigervnc freezes with 100% cpu utilisation #1077
Comments
That's in the clipboard code, so it could be that it has gotten in to some fight with an application. Could you add |
What are you using as a desktop environment within the x.org session? Is it KDE? |
@MarkMielke: I am using LxQt, but it happened with MATE as well (server side). |
Given that it is a clipboard command it does indeed sound suspect. However it's description talks about cut buffers, not clipboard. So it shouldn't be screwing with Xvnc. Did you manage to get that extra logging? |
I removed |
I wonder if the log file message is a second symptom rather than a cause. The reason I mentioned KDE, is because KDE's Klipper has a "Prevent empty clipboard" option that has previously caused us a similar issue. We just turned it off as part of KDE configuration, and I think it might be fixed now. But, at the time - certain scenarios would result some sort of race with each feature fighting the other feature. The reference to QSystemTrayIcon makes me think KDE might be involved - but I'm not aware of whether Klipper is used by LxQt. Possibly |
Thanks for your comments. I am getting this line early at startup:
Later when I select some text in the remote session:
When I start
And finally, when I start |
But no more "Selection" lines? I don't suppose you can see if this happens with stable Debian? |
I was not using TigerVNC recently, but I think I copied all "Selection" lines. |
Very odd. I would expect that if it is stuck in some clipboard war it would be spamming out lines about it. Someone with access to a system like yours would need to take a look and see if they can reproduce this and figure out how to get some traces. |
So this same issue with When the server is running normally, these same two lines are added to the log repeatedly:
After a prolonged period of time if I then try to connect to the server, it freezes up and uses 100% CPU. The log now shows this:
The last line repeats for approx 10,000 lines, interspersed across about a minute of timestamps. Once CPU activity has returned to idle, server is responsive again, and no further log messages appear until I reconnect a client.
The log file then starts repeating the selection requests again as before, even if the client is closed. Will try to explore the issue more this weekend, but suggestions welcome. It seems like there is a build up of selection requests while the server is idle, that then all get responded to at once when a client connects, causing the lock-up. |
This seems likely to be a wider issue with autocutsel - this issue for xrdp sounds almost identical to what I am experiencing. |
Great, I think that gave me a bit more insight in to what's happening here. The good news is that it got fixed in 49122f6. So try a pre-release build, or apply that patch to your builds, and the bug should go away. |
VNC server display gets randomly frozen. Seems to accept no input, no refreshing.
It happened a couple of times, always during active work after a longer time of
vncserver
running.Twice, after a longer while (10min+ but not sure exactly), a freeze was gone and I was able to return to work without any discernible problems.
Xtigervnc
causes 100% CPU utilisation.Other users of the same server (all using tigervnc viewer for Mac) did not encounter such problems.
Strace shows the following displayed at infinitum:
Socket
/tmp/.X11-unix/X2
exists.gdb backtrace
The text was updated successfully, but these errors were encountered: