Compilation continuously increases (non) paged pool memory usage

[Andrey Repin]

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