This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
RE: Possible race condition notes
- To: "'Harold Hunt'" <huntharo at msu dot edu>, "Cygx (E-mail)" <cygwin-xfree at sources dot redhat dot com>
- Subject: RE: Possible race condition notes
- From: Suhaib Siddiqi <ssiddiqi at inspirepharm dot com>
- Date: Mon, 9 Apr 2001 06:38:14 -0400
> 2) Removing all #ifdef __CYGWIN__'d sections from WaitFor.c
> causes XWin to use a normal amount of CPU time, 1-2%,
> when idling; if input events, like mouse clicks and key strokes,
> are entered too quickly, ie. normal typing speed, then
> some of the events will get lost. My favorite window caused
> XWin to crash after closing it 4 times.
Those changes were made because of DirectInput we were using in the previous
version of XWin. Without the changes I made Xsever waited forever
(i.e.WaitForSomething). In other those hacks were needed to work around M$
crap.
However those changes are not needed in win32-x11 and for that server I am
using
orginal WaitFor.c. Have you tested your changes with your DirectX engine?
I
believe you will run into a lot of WaitForSomething weirdness if you use
DirectX engine.
Suhaib
>
> 3) Following step 2, then initializing the timeval structure
> to 0's before the call to Select on line 168 causes XWin.exe
> to consume 100% of available CPU time when idling; XWin
> runs normally
> for all other purposes. My test window caused a crash
> after 43 closes on my first test, on my second and third
> tests I lost count after 80 and gave up on trying to get
> XWin to crash.
>
> 4) Following step 2, then passing Select a NULL for the pointer
> to a time out timeval structure causes xdmcp sessions to consume
> a normal amount of CPU time when idling; however, input events
> get lost if they are entered too quickly, as in 2; closing
> my test window caused a crash on the first close twice in a row,
> and it caused a crash on the second close on the third test.
> Running XWin with local xterm and vtwm clients causes XWin
> to freeze immediately after initializing vtwm and
> displaying the xterm
> window.
>
> I'm not even going to speculate as to what is going on. I
> just wanted to
> get this information out so that other people could look at
> it and comment
> and/or use it as a base for their own bug hunting.
>
> Harold
>