X-Spam-Check-By: sourceware.org Date: Tue, 18 Apr 2006 10:23:33 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: cygwin-1.dll long-time bug Message-ID: <20060418142333.GE12021@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <83c75fec0604180212k3169c7ccua914f7432c4b8ceb AT mail DOT gmail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <83c75fec0604180212k3169c7ccua914f7432c4b8ceb@mail.gmail.com> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Tue, Apr 18, 2006 at 01:12:09PM +0400, burning shadow wrote: >There is a bug in all cygwin processes which leads to 100% CPU usage >and locking another processes. For example, there was a windows update >(installed automatically using Automatic Updates) from Microsoft, >which couldn't be installed until all cygwin processes are stopped. It >happens with some utilities which somehow work with process >information. For example, this happens if I try to see threads tab of >cygwin process in Process Explorer. I thought it was a Process >Explorer's bug, but the same happens with another utilities, and even >with windows updates. Rest assured, that if either Corinna or I ever actually see this problem we'll try very hard to fix it. Until that time, someone else who has the problem is welcome to track it down and offer a patch. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/