Compilation continuously increases (non) paged pool memory usage

Compilation continuously increases (non) paged pool memory usage

[xnor]

Hello,

I've noticed on my system (Windows 10, Cygwin64) that a simple 
./configure && make of a typical project increases the memory usage, 
both paged and non-paged pool.

After the configure/make is done this memory continues to be used. In 
task manager memory usage will therefore slowly grow, depending on the 
projects by up to several GB.

What is leaking here? Is it Windows' fault or Cygwin's?


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

Re: Compilation continuously increases (non) paged pool memory usage

[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?


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

Re: 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

Re[2]: Compilation continuously increases (non) paged pool memory usage

[xnor]

>Greetings, xnor!
Hey.

>Usual suspects are BLODA. Most often, antiviruses of questionable 
>origin and
>mental sanity.
>Try same tests on a separate system, or in a VM.
That's the first thing I've checked. I don't have any anti virus/malware 
or firewall or similar software installed and I've even disabled Windows 
Defender.

Will do some more checks...


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

Re: Compilation continuously increases (non) paged pool memory usage

[Csaba Raduly]

On Tue, Dec 29, 2015 at 7:38 PM, xnor wrote:

> What is leaking here?

> How could I debug better what is leaking here?

Have you tried looking at the memory usage of processes in Process Explorer?

-- 
GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++
The Tao of math: The numbers you can count are not the real numbers.
Life is complex, with real and imaginary parts.
"Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds
"People disagree with me. I just ignore them." -- Linus Torvalds

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