This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
RE: More notes on client exit causing 100% cpu usage
- To: "CygX (E-mail)" <cygwin-xfree at sources dot redhat dot com>
- Subject: RE: More notes on client exit causing 100% cpu usage
- From: Lundh Christian <Christian dot Lundh at volvo dot com>
- Date: Thu, 5 Apr 2001 08:53:29 +0200
I know recent mailers claim they have solved this problem. I just want to
throw in my experiences on this subject.
I had this problems a long time. Then I noticed than when I started X from
dos/NT (using startxwin.bat) the shell used is /bin/sh and everytime I exit
an xterm it hangs. When I start from cygwin using my own start script (which
just starts the xserver and the window manager) i get /bin/bash as my shell
and I xterm never hangs on exit.
Perhaps I'm lucky, perhaps I'm wrong. Just wanted you to know this.
/Christian Lundh
-----Original Message-----
From: Christopher Faylor [mailto:cgf@redhat.com]
Sent: Wednesday, April 04, 2001 11:23 PM
To: cygwin-xfree@cygwin.com
Subject: Re: More notes on client exit causing 100% cpu usage
On Wed, Apr 04, 2001 at 11:41:28AM -0400, Harold Hunt wrote:
>Suhaib,
>
>Yup, that is with test 15.
>
>Typing 'exit' into an xterm doesn't cause this everytime... it appears to
be
>a race condition so your mileage will vary depending on how fast your
>machine and its various subsystems are.
>
>Sometimes I get lucky and the first xterm will crash when I exit it, but
>usually I have to open and close about ten xterms before I can get one to
>crash on exit.
>
>Note that this happens with rxvt as well...
Does this happen with a recent Cygwin snapshot? I wonder if this could
be a pty race that was recently fixed.
cgf