On Fri, 1 Nov 2002, Vlad Harchev wrote:
> Hi,
>
> I'm using Xvnc-3.3.3 from redhat-7.2 for x86 (package name is
> vnc-server-3.3.3r2-18).
> I encounter the following problem with it:
>
> Sometimes Xvnc begins eating 100% CPU. Stracing it I get the following loop
> (2 cycles shown):
>
> time(NULL) = 1026840822
> select(128, [0 1 3 5 6 7 8], NULL, NULL, {0, 0}) = 0 (Timeout)
> select(4, [3], NULL, NULL, {0, 0}) = 0 (Timeout)
> gettimeofday({1026840822, 9415}, NULL) = 0
> time(NULL) = 1026840822
> select(128, [0 1 3 5 6 7 8], NULL, NULL, {0, 0}) = 0 (Timeout)
> select(4, [3], NULL, NULL, {0, 0}) = 0 (Timeout)
> gettimeofday({1026840822, 9622}, NULL) = 0
>
> In such state Xvnc perfectly accepts connections from vncviewers, and works
> fine.
>
> Only killing Xvnc stops it from eating all CPU.
>
> As I observed, Xvnc switches to this state in the following conditions:
> 1) Either 1 week or more of process life.
> 2) Changing the time on the box (e.g. increasing current system time by a
> couple of minutes using 'date -s').
> It seems condition 1 is necessary, and condition 2 is not necessary provided
> condition 1 takes place.
>
> There are several Xvncs running on that box - they are started at the same
> time (with precission of several seconds), and they begin eating CPU almost at
> the same time. Not all Xvncs that switch to that state are connected to - one
> of Xvncs is run for programs just to have $DISPLAY pointing somewhere, and
> it's started as "Xvnc -ac -depth 8 -geometry 20x20 -fp
> tcp/localhost:7100 :8" and NO apps draw windows on it at all too, and it also
> begins eating CPU too. Other Xvncs are run using following commandline:
> "Xvnc -fp tcp/localhost:7100 -pixelformat rgb565 -depth 16 -geometry 1024x768"
>
> Here is a stderr output of the Xvnc that nobody was connecting to:
> ------
> started at Oct 22 18:12:31 2002
> 22/10/02 18:12:31 Xvnc version 3.3.3r2+tight1.1p9
> 22/10/02 18:12:31 Copyright (C) AT&T Laboratories Cambridge.
> 22/10/02 18:12:31 All Rights Reserved.
> 22/10/02 18:12:31 See http://www.uk.research.att.com/vnc for information on
> VNC
> 22/10/02 18:12:31 Desktop name 'x11' (srv:8)
> 22/10/02 18:12:31 Protocol version supported 3.3
> 22/10/02 18:12:31 Listening for VNC connections on TCP port 5908
> -------
> As you can see, the log is empty (no connections were made to this Xvnc).
> It started eating all CPU on oct 31 between 21:30 and 21:40 (I'm using
> reports provided by sar(1)).
I'm sorry, I forgot to add that I changed the system time (increaded by 5
minutes) on Oct 31 21:36. So it seems Xvnc began eating all CPU
almost immedeately..
Best regards,
-Vlad
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list
