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

2006-12-08 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Dave Silvia on 12/8/2006 10:16 AM: > The list you gave above has an ellipsis, usually denoting there are more. Is > there a place where this list is kept? The mailing list archives. The list of problem drivers is ad hoc; it continues to

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

2006-12-08 Thread Larry Hall (Cygwin)
Dave Silvia wrote: -- On Thu, 07 Dec 2006 06:36:05 -0700 Eric Blake wrote -- 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 lea

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

2006-12-08 Thread Dave Silvia
> -- On Thu, 07 Dec 2006 06:36:05 -0700 Eric Blake wrote -- > >> 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 me

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

2006-12-07 Thread Dave Korn
On 07 December 2006 18:30, Dave Silvia wrote: > 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.

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

2006-12-07 Thread Dave Silvia
-- 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 >>

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

2006-12-07 Thread Matt Wozniski
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 memor

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

2006-12-07 Thread Dave Korn
On 07 December 2006 13:08, Dave Silvia wrote: > 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

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

2006-12-07 Thread Eric Blake
-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 li

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

2006-12-07 Thread Dave Silvia
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): -- #!/bin/sh if [ "$1"