public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: xnor <xnoreq@gmail.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Compilation continuously increases (non) paged pool memory usage
Date: Tue, 29 Dec 2015 01:12:00 -0000	[thread overview]
Message-ID: <em5a95f282-d756-462f-ae8d-ec1b1f228af5@gaming> (raw)

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

             reply	other threads:[~2015-12-29  1:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-29  1:12 xnor [this message]
2015-12-29 17:38 ` xnor
2015-12-29 19:50   ` Andrey Repin
2015-12-29 19:58     ` Re[2]: " xnor
2015-12-30 13:22   ` Csaba Raduly

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=em5a95f282-d756-462f-ae8d-ec1b1f228af5@gaming \
    --to=xnoreq@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).