X-Spam-Check-By: sourceware.org
From: Dave Silvia <dsilvia AT mchsi DOT com>
To: Eric Blake <ebb9 AT byu DOT net>, cygwin general mailing list <cygwin AT cygwin DOT com>,
   Dave Silvia <dsilvia AT mchsi DOT com>
X-Mailer: Barca Pro 2.1 (3650) - Licensed Version
Date: Thu, 7 Dec 2006 12:29:37 -0600
Message-ID: <2006127122937.636936@privateconcern>
In-Reply-To: <457818C5.2040708@byu.net>
Subject: Re: 1.5.21-1 Release: Windows memory resources do not recover.
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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
Note-from-DJ: This may be spam
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id kB7ITgLb028904

-- On Thu, 07 Dec 2006 06:36:05 -0700 Eric Blake wrote --
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> According to Dave Silvia on 12/7/2006 6:08 AM:
>> Hi!
>>
>> On further investigation an looking more closely at the areas in
>> the configure script where they errors and/or reboot was
>> occurring, and with some helpful pointers from responders on this
>> list, I've constructed the following bash shell script
>> (exhaustMem.bsh):
>>
>
> Are you SURE you don't have a buggy driver installed?  Known
> culprits include Agnitum outpust, Mcafee virus scanners, Logitech
> webcam, ...  In other words, the leak is not caused by cygwin, but
> by your buggy driver leaking memory for every process spawned by
> your process-intensive scripts.
>
> - --
> Life is short - so eat dessert first!
>
> Eric Blake             ebb9 AT byu DOT net
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Cygwin)
> Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFFeBjF84KuGfSFAYARAg0cAKCPRB3toLdIVa1FVzROuhqrK5EKYQCdHIod
> H5WTYFZH4SFoaRgm1X6QvGQ= =dWdL -----END PGP SIGNATURE-----

Well, if there's a conflict with a driver or service, it's a Microsoft driver or
service because that's all that appears to be running differently between Safe
and Normal mode. And, yes, in Safe mode it doesn't exhibit the behavior, but
that's hardly helpful. I don't imagine anyone who's going to run major
configuration scripts is going to want to do it in safe mode. Nor would it be
desirable/effective in a lot of instances.

It does appear to be some kind of problem between bash and Windows. I'm done,
tho'. It's beyond my resources to do anything about and I haven't any more time
to spend on investigating other shells to see if they're different. 3 days is
enough.

thx,
Dave S.


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