X-Spam-Check-By: sourceware.org
Message-ID: <83c75fec0604180212k3169c7ccua914f7432c4b8ceb@mail.gmail.com>
Date: Tue, 18 Apr 2006 13:12:09 +0400
From: "burning shadow" <burning DOT shadow AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: cygwin-1.dll long-time bug
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Disposition: inline
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id k3I9CJXh018213

There is a bug in all cygwin processes which leads to 100% CPU usageand 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. Ithappens with some utilities which somehow work with processinformation. For example, this happens if I try to see threads tab ofcygwin process in Process Explorer. I thought it was a ProcessExplorer's bug, but the same happens with another utilities, and evenwith windows updates.