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
To: cygwin AT cygwin DOT com
From: Andrew DeFaria <Andrew AT DeFaria DOT com>
Subject: Re: Excessive CPU load (cygrunsrv.exe, tail.exe, etc)
Date: Thu, 30 Sep 2004 17:17:59 -0700
Lines: 44
Message-ID: <cji7je$n7g$1@sea.gmane.org>
References: <20040930210025 DOT 87264 DOT qmail AT web52304 DOT mail DOT yahoo DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet AT sea DOT gmane DOT org
X-Gmane-NNTP-Posting-Host: 12.9.207.207
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
In-Reply-To: <20040930210025.87264.qmail@web52304.mail.yahoo.com>
X-IsSubscribed: yes

Steve B wrote:

> I do not believe that I am using Process Explorer.

So then it's apparently not required that Process Explorer be running to 
trigger this process.

> This CPU load overload can reliably be triggered by Enemy Territory. 
> Guaranteed, every time I run Enemy Territory, a cygwin process will 
> begin to hog the CPU starting with cygrunsrv.exe every time, and will 
> continue until either a) I keep killing (through the Windows task 
> manager) each cygwin process that overloads until no more cygwin 
> process exists so I can return to my game, or b) I terminate Enemy 
> Territory through the Windows task manager and kill the cygwin process 
> that is overloading, then no other cygwin processes will hog the cpu, 
> but I cannot play Enemy Territory. 

Well that's easy then. Stop playing games! :-)

Seriously though, maybe Enemy Territory is interrogating the process 
table in a similar manner as Process Explorer is.

> I thought that since it could reliably be triggered this way, perhaps 
> that might assist with any testing, if any.
>
> Another thing I noticed, after reading Andrew DeFaria post, was that 
> csrss.exe would be using 25% of the CPU while the cygwin processes 
> would hog about %75 of the CPU. I'm not sure what csrss.exe is,

http://www.liutilities.com/products/wintaskspro/processlibrary/csrss/

    csrss.exe is the main executable for the Microsoft Client/Server
    Runtime Server Subsystem. This process manages most graphical
    commands in Windows. This program is important for the stable and
    secure running of your computer and should not be terminated.

> except that I cannot kill it (Access Denied, even as Administrator).

That's what Process Explorer is for! It can kill things that the Task 
Manager won't let you. Unfortunately killing some things, like this, is 
very determental to your system (i.e. you reboot! IIRC).

-- 
Why isn't 11 pronounced "onety one"?


--
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/