This is the mail archive of the cygwin@sources.redhat.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: idle bash using 95% of system resources?


Johanthan,

This suggests a work-around until the problem can be found and fixed: 
Set the "notify" option in BASH (i.e., issue the command "set 
notify"). That way BASH prints jobs status changes when they occur, 
instead of waiting for the next time it prints a prompt.

Randall Schulz
Teknowledge Corp.
Palo Alto, CA USA


At 16:35 -0500 10/11/00, Jonathan M Merz wrote:
>On Wed, Oct 11, 2000 at 09:57:16PM +0100, Henry S. Thompson wrote:
>>  I'm running netinstalled 1.1.4, including bash 2.04.0, under Win2K.
>>
>>  I've modified cygwin.bat as follows:
>>
>>      C:
>>      chdir \cygwin\bin
>>      set CYGWIN=tty
>>      bash --login -i
>>
>>  After running for a fair while, I find that I lose performance across
>>  the board, and that bash is the culprit:  although it's still working
>>  OK, the Windows Task Manager shows 90--95% of CPU going to bash.
>>
>>  Anybody else seen this?
>>
>
>I've seen something that may be the same running cygwin 1.1.4 on 
>both WinNT 4 and Win98.  If I start an
>external program and fork it from the shell, i.e:
>    gvim.exe &
>
>, and then exit gvim, bash eats up the CPU until I hit return at the 
>prompt to allow the
>     "[1]+  Done        gvim"
>message to print.  After the message is shown, things seem to run 
>ok, but bash does eat up the CPU
>until the message prints.o
>
>-Jon



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]