From 61cd498fb21b5b2a3f63f336b1f1ed297f451c22 Mon Sep 17 00:00:00 2001 From: dscho Date: Sat, 17 Mar 2007 00:13:12 +0000 Subject: Fix a locking problem in libvncserver There seems to be a locking problem in libvncserver, with respect to how condition variables are used. On certain machines in our lab, when using a vncviewer to view a display that has a very high rate of updates, we will occasionally see the VNC server process crash. In one stack trace that was obtained, an assertion had tripped in glibc's pthread_cond_wait, which was called from clientOutput. Inspection of clientOutput suggests that WAIT is being called incorrectly. The mutex that protects a condition variable should always be locked when calling wait, and on return from the wait will still be locked. The attached patch fixes the locking around this condition variable, and one other that I found by grepping the source for similar occurrences. Signed-off-by: Charles Coffing --- ChangeLog | 3 +++ 1 file changed, 3 insertions(+) (limited to 'ChangeLog') diff --git a/ChangeLog b/ChangeLog index d654589..b2f7a1d 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,6 @@ +2007-03-17 Charles Coffing + * libvncserver: fix a locking issue + 2007-02-01 Johannes E. Schindelin * libvncclient: add updateRect member to rfbClient, to allow requesting smaller updates than whole-screen. -- cgit v1.2.1