X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Mon, 29 Nov 2010 21:57:08 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: tcsh out of memory and core dump
Message-ID:	<20101129205708.GA18309@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<4CF3A393 DOT 3060807 AT qwestoffice DOT net>
MIME-Version:	1.0
In-Reply-To:	<4CF3A393.3060807@qwestoffice.net>
User-Agent:	Mutt/1.5.20 (2009-06-14)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On Nov 29 05:58, tsteven4 wrote:
> I can readily reproduce a tcsh error "Out of memory", however the
> timing is variable.  In my actual application the time to failure
> varies from seconds to hours.  I have a test case that seems to be
> able to reproduce the error.
> 
> The symptom of the error is a message like:
> 188
> ./test2
> 189
> ./test2
> 190
> ./test2
> 191
> tcsh current memory allocation:
> free:       0  119   52   25   29   23   17    3    0    2    0    0
> 2    0    0    0    0    0    0    0    0    0    0    0    0    0
> 0    0    0
> used:       0    9  204  167   51   33   19    3    1    1    2    2
> 1    4    3    0    0    0    0    0    0    0    0    0    0    0
> 0    0    0
>         Total in use: 788560, total free: 100272
>         Allocated memory from 0xab0000 to 0xffffffff.  Real top at 0xb89000
> nbytes=32784: Out of memory
> Abort (core dumped)
> 192
> ./test2
> 193
> ./test2
> 194
> ./test2
> 195
> ./test2

Thanks for the testcase!  It helped me to track down a memory leak in
Cygwin which occurs on each dup/dup2/dup3 call on a tty.  This is done
very often in tcsh and thus affects long-running scripts quite heavily.

I applied a patch to CVS.  Please test the next Cygwin developer snapshot
from http://cygwin.com/snapshots/, which will contain the fix.


Thanks again,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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

- Raw text -