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:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; q=dns; s=default; b=et8QKMNI/kskmiGhs2QpTVktmmJr
	X/xtwIhdhFA+YboNXZXRkNAGfSCt6ody+PlU5aqTPQunWASwlG40OQBCnJCYWIxN
	IcqrygvmRhqbGKyVOeKO9yCiFamGQGgiFdpp6FJM6L0LIBWE/eM1rhCw65zXkOsO
	TzpDNDvHgaXAz0I=
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:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; s=default; bh=u8t2ALq9dC65fqPa5PERIzWm52c=; b=X2
	wYoLj0u50QB9nmg0u6fslrukx2uRgwxi7qY+PUdVAT7+OAD/RdxPaDtbVR0oydaB
	rraiVbmS4Js3hdGJquNHmN3hLIUDyOzu333DZCUcRUNQEtSbl/Yh4NKpWqRCKxPW
	Dg9rMUnQuxtlz6AkO/jicFirusKAYUbzeBHQ5GV+0=
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.8 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,T_RP_MATCHES_RCVD autolearn=no version=3.3.2
X-HELO: etr-usa.com
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
Subject: Re: cygwin memory leak
From: Warren Young <wyml AT etr-usa DOT com>
In-Reply-To: <192042331.20150611220629@morauf.de>
Date: Thu, 11 Jun 2015 16:16:13 -0600
Message-Id: <160B707E-6BFC-4AD5-BBE0-56F810C13C94@etr-usa.com>
References: <192042331 DOT 20150611220629 AT morauf DOT de>
To: The Cygwin Mailing List <cygwin AT cygwin DOT com>
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t5BMGRGD024848

On Jun 11, 2015, at 2:06 PM, Frank Morauf <frank AT morauf DOT de> wrote:
> 
> Running the following lines let windows physical memory grow until no
> more left (task-manager: physical memory).

I’ve run it here in two separate sessions of about 10 minutes each.  Memory usage isn’t growing.  Windows 10 preview, 64-bit OS and 64-bit Cygwin.

> The taken memory is never
> freed until os restart.

I don’t think Cygwin could do that even if it wanted to, given that you don’t have any Cygwin services running.  Once the last Cygwin process dies, the OS *will* release the memory it was holding.

cygcheck didn’t seem to find any BLODA on your system, but that seems a more likely explanation than that Cygwin — a purely user-space program — has somehow caused a kernel-level memory leak.

> Tested on three different Windows 7 x64 machines with actual
> cygwin 2.x (32 and 64 bit).

Try testing with all antimalware software disabled, or better, uninstalled.
--
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