Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
X-Authentication-Warning:	eos.vss.fsi.com: ford owned process doing -bs
Date:	Tue, 27 Jan 2004 10:22:48 -0600 (CST)
From:	Brian Ford <ford AT vss DOT fsi DOT com>
X-X-Sender:	ford AT eos
To:	Steven Hartland <killing AT multiplay DOT co DOT uk>
cc:	cygwin AT cygwin DOT com
Subject:	Re: cygwin processes and system'ed processes using 100% CPU
In-Reply-To:	<01c601c3e4e3$f186d380$b3db87d4@multiplay.co.uk>
Message-ID:	<Pine.GSO.4.58.0401271014580.11773@eos>
References:	<40164D3D DOT 3080601 AT dynaware DOT de> <20040127122719 DOT GH2120 AT bln DOT sesa DOT de> <Pine DOT GSO DOT 4 DOT 56 DOT 0401270841580 DOT 2972 AT slinky DOT cs DOT nyu DOT edu> <01c601c3e4e3$f186d380$b3db87d4 AT multiplay DOT co DOT uk>
MIME-Version:	1.0
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com

Please start a new thread rather than replying to an old one for new
issues.

On Tue, 27 Jan 2004, Steven Hartland wrote:

> General question has anyone else seen processes running under
> cygwin using 100% CPU when the shouldn't.
> The background is cygwin 1.5.5 I have a perl script which
> monitors process cpu levels. It does this using serveral system
> calls to other utils, ps, vmstat and pslist ( win32 app from
> sysinternals ). The script samples every minute recording the
> results.
> Now 99% of the time all is fine but sometime when actually
> running ( every minute ) it and the utils it spawns most notablly
> pslist use 100% cpu. So much so that if you have the desktop
> open it will freeze for the few seconds that its sampling for.
> Its very strange once its doing it it will continue to do so for each
> sample until restarted. The only pattern I can see so far is that
> it tends to happen when said script is started from sub shell
> script via a ssh -l user "restart.sh"
>
> Anyone seen anything similar? Alternatively what do people
> think is the best approch to find the issue? On FreeBSD truss
> would be my first port of call.
>
On Cygwin, I would suggest "man strace".

> Thanks for that Brian I was avoiding 1.5.6 due to the amount of issues
> I've seen flying around with it. Looks like they have settled with -1 so
> I will try upgrading 1 machine and see if I can reproduce. Cheers.
>
That is/was probably a good idea, but please test with the latest
snapshot.  See http://cygwin.com/snapshots for details.  Thanks.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444

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

- Raw text -