1.5.21-1 Release: Windows memory resources do not recover.

Dave Silvia dsilvia@mchsi.com
Thu Dec 7 18:29:00 GMT 2006

-- On Thu, 07 Dec 2006 06:36:05 -0700 Eric Blake wrote --
> 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@byu.net
> 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

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

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/

More information about the Cygwin mailing list