Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date: Thu, 7 Aug 2003 22:48:57 -0400
From: Christopher Faylor <cgf-idd AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Win2k and cygwin memory leak
Message-ID: <20030808024857.GB10258@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <OFAB076707 DOT BB79F906-ON85256D7B DOT 007195C4 AT empirehealthcare DOT com> <bguji2$l5q$1 AT main DOT gmane DOT org> <20030808014303 DOT GA3528 AT Orlyn>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030808014303.GA3528@Orlyn>
User-Agent: Mutt/1.4.1i

On Fri, Aug 08, 2003 at 03:44:11AM +0200, Luc Hermitte wrote:
>* On Thu, Aug 07, 2003 at 03:24:26PM -0700, Andrew DeFaria <ADeFaria AT Salira DOT com> wrote:
>>It has already been acknowledged several times over that it is not a
>>problem of Cygwin's rather a problem of Windows.
>
>I think we all agree to that.  But unfortunatelly, so far, only Cygwin
>seems affected by that problem.

You're referencing facts not in evidence.  We don't know that it is only
Cygwin.  I haven't seen any evidence that anyone has done any research
on this.  We don't know that this isn't triggered by something as simple
as a virus checker.

>> When you cluelessly continue to assert that it's a Cygwin memory leak
>> is exactly where is leads down the path to character assassinations.
>
>Could we say that cygwin relies on a faulty library developped by
>Microsoft ? And that nobody has identified the faulty library ?

Saying this would be pure speculation.

Just as an observation: I went to the RAMpage home page and, curiously,
it does not prominently mention cygwin.  In fact, I couldn't find a
mention of cygwin at all.  If this was a problem that only manifested
with cygwin programs, I would think that RAMpage would mention that
fact.

Looking at RAMpage's code and reading the description, I see nothing
that indicates it would solve this supposed "memory leak" problem.  All
that it does is allocate a huge chunk of memory and free it, forcing any
fragmented memory out onto disk.  I really don't see how that would
cause any improvement in anything related to a memory leak.

cgf

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