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
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: Tracking down process/memory leak
Date: Thu, 21 Apr 2005 17:52:22 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
In-reply-to: <d6517a4309ce5660a2f1d7c253fb041e@oculustech.com>
Message-ID: <SERRANOWdVBdQoT0IfJ000000a3@SERRANO.CAM.ARTIMI.COM>
X-OriginalArrivalTime: 21 Apr 2005 16:52:25.0254 (UTC) FILETIME=[7E912C60:01C54692]

----Original Message----
>From: Timothy Wall
>Sent: 19 April 2005 16:05

> I've used msconfig to turn off all services/drivers at startup, and the
> memory leak persists.  Kernel memory goes up slowly, Physical memory
> goes down faster, and Handles/Threads/Processes remain steady.
> 
> I'm not aware of any software installed which might have an effect on
> spawned processes.  Aside from sshd and vncd, the apps installed are
> standalone applications with no associated services or system addons.


  You should try and find out *which* application is leaking this memory.
The fact that kernel memory is involved very much suggests a faulty device
driver.

  Anyway, the way to find out is to fire up task manager (I assume that's
what you're using already to determine that kernel memory is increasing),
and go to the "View" menu and click "Select columns".  Tick the boxes next
to "Paged Pool" and "Non-paged Pool", which are the two types of kernel
memory included in that total figure, and then try and figure out which
application is actually consuming it by watching the columns for a while and
seeing which line the figures are going steadily up on.

  At that time it'll probably turn out that this is nothing to do with
cygwin at all and we'll be off-topic, but it's certainly the first next step
to try.




    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


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