-
Notifications
You must be signed in to change notification settings - Fork 922
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 #1551
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
We've updated that code a fair bit since 1.11.0. Do you think you could try 1.12.0, or a nightly build? It looks like it is trying to send clipboard data when this happens. Have you noticed if this happens when you do something specific? Is Xvnc consuming a lot of CPU when this happens? And is the viewer locked up as well? |
This comment was marked as off-topic.
This comment was marked as off-topic.
We've updated that code a fair bit since 1.11.0. Do you think you could
try 1.12.0, or a nightly build?
I can give that a try.
>It looks like it is trying to send clipboard data when this happens. Have
you noticed if this happens when you do something specific?
No, we don't have specific step(s) to reproduce this issue.
Is Xvnc consuming a lot of CPU when this happens?
No, normal cpu load for Xvnc.
And is the viewer locked up as well?
Yes, all clients are locked up.
I don't understand why an issue in the clipboard is locking up all vnc
clients?
…On Mon, 21 Nov 2022 at 14:26, Pierre Ossman (Work account) < ***@***.***> wrote:
We've updated that code a fair bit since 1.11.0. Do you think you could
try 1.12.0, or a nightly build?
It looks like it is trying to send clipboard data when this happens. Have
you noticed if this happens when you do something specific?
Is Xvnc consuming a lot of CPU when this happens?
And is the viewer locked up as well?
—
Reply to this email directly, view it on GitHub
<#1551 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4IOBLPU7JEC6L7HXYJFU6DWJN2B3ANCNFSM6AAAAAASESSNGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I probably need to clarify this a bit, with a locked up client I mean that you cannot interact with the client at all. E.g. you can't even close the viewer or open the F8 menu.
It shouldn't. This is some form of bug. But we need to figure out what is triggering it in order to come up with a fix. |
Yes, all clients are locked up.
I probably need to clarify this a bit, with a locked up client I mean that
you cannot interact with the client at all. E.g. you can't even close the
viewer or open the F8 menu.
We can still close the viewer.
To summarize:
- All vnc-viewers connected to this vnc server don't get any screen updates
no interaction possible for a period between 1 min and 16 min
- after that VNC freeze we can continue as normal
- During the vnc freeze the CPU load of the vncserver is low
- stacktrace shows that Xvnc tries to flush its clipboard buffer, but since
there is no space it keeps looping in a select() call with 5ms timeout
Any ideas how I can debug this further?
…On Thu, 24 Nov 2022 at 16:23, Pierre Ossman (Work account) < ***@***.***> wrote:
Yes, all clients are locked up.
I probably need to clarify this a bit, with a locked up client I mean that
you cannot interact with the client at all. E.g. you can't even close the
viewer or open the F8 menu.
I don't understand why an issue in the clipboard is locking up all vnc
clients?
It shouldn't. This is some form of bug. But we need to figure out what is
triggering it in order to come up with a fix.
—
Reply to this email directly, view it on GitHub
<#1551 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A4IOBLNEVVWM3445RUYVJ2TWJ6CAVANCNFSM6AAAAAASESSNGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
All right, so for some reason it thinks there is a lot of clipboard data. Could you check bandwidth usage when this happens? Does it seem to be hogging all available capacity? And could you try 1.12.0? We redid a lot of the network handling there. |
Short update on this issue: Thanks for your help. |
Glad to hear that. Thanks for testing. |
@erikniessen I can still see either this or a similar issue with 1.12.0. Basically the screen suddenly freezes and this is not in the middle of any particular operation. I'm using VNC viewer on Windows connecting to tigervnc 1.12.0 on Ubuntu 22.04. My settings are basically out-of-the-box without a custom xstartup file, etc. Once the session hangs, killing the session and trying to create a new session shows the error "Session startup via '/etc/X11/Xtigervnc-session' cleanly exited too early (< 3 seconds)!" What additional information can I provide for debugging? |
Describe the bug
VNC server display gets randomly frozen. Seems to accept no input, no refreshing.
It happened a couple of times/day, always during active work.
Freeze happens between 1min and 10 min after that I was able to return to work without any problems.
Same freeze happens on different machines running the same sw.
Client:
Server :
/usr/bin/Xvnc :1 -alwaysshared -idletimeout 0 -listen tcp -securitytypes None -auth $HOME/.Xauthority -desktop $HOSTNAME:1 ($USER) -fp catalogue:/etc/X11/fontpath.d -geometry 1920x1080 -pn -rfbauth $HOME/.vnc/passwd -rfbport 5901 -rfbwait 30000 -desktop :1 -rfbport 5910
Additional context
pstack output of Xvnc
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: