This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Compilation continuously increases (non) paged pool memory usage
- From: Andrey Repin <anrdaemon at yandex dot ru>
- To: xnor <xnoreq at gmail dot com>, cygwin at cygwin dot com
- Date: Tue, 29 Dec 2015 22:38:00 +0300
- Subject: Re: Compilation continuously increases (non) paged pool memory usage
- Authentication-results: sourceware.org; auth=none
- References: <em5a95f282-d756-462f-ae8d-ec1b1f228af5 at gaming> <em5d8d58f8-9aaf-47d9-a26c-8f3620bcc50e at gaming>
- Reply-to: cygwin at cygwin dot com
Greetings, xnor!
>>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?
Usual suspects are BLODA. Most often, antiviruses of questionable origin and
mental sanity.
Try same tests on a separate system, or in a VM.
--
With best regards,
Andrey Repin
Tuesday, December 29, 2015 22:37:01
Sorry for my terrible english...
--
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