delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2015/12/29/12:38:53

X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
:list-unsubscribe:list-subscribe:list-archive:list-post
:list-help:sender:from:to:subject:date:message-id:in-reply-to
:reply-to:mime-version:content-type:content-transfer-encoding;
q=dns; s=default; b=KOymJPTh+/3QdAlzsuBr+dXiaXNgBmkhBLQ75w3IriF
KcKSA2x4u54cHJoqjFtwY70WsGf6QHBAvfcvBIjGw+KbWeef8K2t4EigbqZ+KeLN
NceJOPdB5wvIaikOypcvFW7+6tkUZ4ehMyJWMP3BKPzenc46YMtDSaUSITzpbzNQ
=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
:list-unsubscribe:list-subscribe:list-archive:list-post
:list-help:sender:from:to:subject:date:message-id:in-reply-to
:reply-to:mime-version:content-type:content-transfer-encoding;
s=default; bh=gTes6r2fm+gwFEFR6ScDoVk+trk=; b=G4N7/nx2C1MWVhRzs
5AEftjsiSyPKfT72uA4/v4JOZnGv/WPs1KnEVPBEwRuKAn83Ba3lMrHyebDIHtm2
vue/eN14+wUtmoAlGUWeVOkkpk6gLXDh+cHJk0TCSVYooV5GKqcIMqs+1pM5nmio
dVp8zn8s6mD5T8MpXLlZC3zPaE=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-0.2 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=650, 249, Compilation, H*i:sk:em5a95f
X-HELO: mail-wm0-f41.google.com
X-Received: by 10.195.11.101 with SMTP id eh5mr66423286wjd.104.1451410710707; Tue, 29 Dec 2015 09:38:30 -0800 (PST)
From: xnor <xnoreq AT gmail DOT com>
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: Re: Compilation continuously increases (non) paged pool memory usage
Date: Tue, 29 Dec 2015 17:38:46 +0000
Message-Id: <em5d8d58f8-9aaf-47d9-a26c-8f3620bcc50e@gaming>
In-Reply-To: <em5a95f282-d756-462f-ae8d-ec1b1f228af5@gaming>
Reply-To: xnor <xnoreq AT gmail DOT com>
User-Agent: eM_Client/6.0.24144.0
Mime-Version: 1.0
X-IsSubscribed: yes
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id tBTHcoPL011022

>What is leaking here?
Here are some hard numbers:
After the system booted up, nonpaged 70 MB, paged WS 208 MB.
One compilation later: nonpaged 157MB, paged WS 289 MB.
Another one later: 249 MB, 342 MB.
At the moment I'm at 550 MB nonpaged, 650 MB paged WS.

The number of system threads and handles remains about the same.
poolmon shows the main growth of nonpaged memory with tag "Proc" 
(process objects) and paged with tag "Toke" (token objects).

xperf shows cygwin1.dll under Proc.

How could I debug better what is leaking here?


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple


- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019