Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com From: Chris Faylor Date: Fri, 11 Aug 2000 11:40:59 -0400 To: "Cygwin (E-mail)" Subject: Re: processor high use in cygwin 1.1.4 or bash Message-ID: <20000811114059.F19565@cygnus.com> Reply-To: cygwin AT sources DOT redhat DOT com Mail-Followup-To: "Cygwin (E-mail)" References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: ; from cbjones@nortelnetworks.com on Fri, Aug 11, 2000 at 07:19:57AM -0400 On Fri, Aug 11, 2000 at 07:19:57AM -0400, Christopher Jones wrote: >I've noticed that when I run a Windows application via bash in the >background (ie putty &) that once the program exits csrss.exe and bash.exe >each consume roughly 50% of the processor according to task manager until I >press the return key in the bash window and get the "[1] Done >putty" message. > >However, not to let anyone just blow this off as a Windows app problem, the >same thing happens when I run "gdb &" and exit gdb but do not press return >or do something else in the bash window... bash and csrss do the same thing >again, together consuming all of the available processor. It looks like any process which exits in the background causes the same behavior. It doesn't seem to be a problem in the CVS sources but I certainly haven't done anything to either cause or fix this. Weird. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com