Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Message-ID: <42CB69DC.9DF06F01@dessent.net>
Date: Tue, 05 Jul 2005 22:19:24 -0700
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Please try latest snapshot -- pthreads mutex users please note
References: <BAY107-F307C877027AAD7DFDBEBBD6D90 AT phx DOT gbl>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Report: -5.9/5.0 ---- Start SpamAssassin results  	* -3.3 ALL_TRUSTED Did not pass through any untrusted hosts 	* -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% 	*      [score: 0.0000] 	*  0.0 AWL AWL: From: address is in the auto white-list 	---- End SpamAssassin results
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Arash Partow wrote:

> I've done a clean install of cygwin with dll 1.5.18 and also tried
> snapshots from 2nd, 4th and 5th. Unfortunetly issues relating to
> threading and memory leaks as described in the following post - still
> exists:
> 
> http://sources.redhat.com/ml/cygwin/2005-06/msg00186.html

I don't believe this is a valid test case.  It has a severe memory leak,
that's definite.  But it does the exact same thing under Linux:

$ ./example1 >/dev/null & thepid=$! ; while cat /proc/$thepid/stat | awk
'{ print $24*4 }'; do sleep 3; done                      [1] 1310
1088
61820
136244
206468
0
[1]+  Bus error               ./example1 >/dev/null
cat: /proc/1310/stat: No such file or directory

This runs the program and prints its RSS in Kbytes every three seconds. 
As you can see it very quickly consumes all memory and crashes to a
halt.  Whatever this problem is, I do not think it's related to Cygwin
in any way, except for the fact that it takes much longer under Cygwin
to exhaust all memory due to the slower pthread locking compared to
Linux.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/