RE: Huge memory leak, probably related to making new processes

2007-10-03 Thread wimxa
Dave, I take that back - it still might be one from your list. The machine has Symantec antivirus - it was hidden behind the "Show hidden icons". (Doh, I am making too many obvious mistakes.) I'm not an admin, so I cannot check which one - maybe both? The machine doesn't seem to have PC Tool's Sp

RE: Huge memory leak, probably related to making new processes

2007-10-03 Thread wimxa
Dave, Nope, this one is called Webroot Spy Sweeper (if it is the problem with it). -- View this message in context: http://www.nabble.com/Huge-memory-leak%2C-probably-related-to-making-new-processes-tf4557470.html#a13019192 Sent from the Cygwin Users mailing list archive at Nabble.com. --

RE: Huge memory leak, probably related to making new processes

2007-10-03 Thread wimxa
I have just tried this on another machine with Cygwin - no leaks. OK, so it is not Cygwin - my bad, but I'm glad. Just to test, I have made a script for WIndows' cmd.exe: @echo off set c=1 :loop cmd /c echo > nul echo %c% set /a c=%c%+1 if %c%==123456 goto end goto loop :end Leaks... Not so fa

RE: Huge memory leak, probably related to making new processes

2007-10-03 Thread wimxa
Guys, Thank you for the trouble of testing this. Unfortunately, I cannot confirm whether this is a problem with any AV - I am not an admin on the machine in question, cannot shut AV down. About the kernel memory figures - they are increasing - much slower and in a very unpredictable see-saw way

Re: Huge memory leak, probably related to making new processes

2007-10-02 Thread wimxa
> How do you know it is leaking memory? If you are looking at Windows Task Manager or some similar program, then you're probably just being misled. The OS will automatically free the memory from each "echo" process after it terminates, but it may not always immediately report it as available.

Huge memory leak, probably related to making new processes

2007-10-02 Thread wimxa
Try executing: find -exec echo {} \; Simple command. This one, however, leaks at about 5kB/s. I tried the following: find|xargs echo This one didn't appear to leak, but then I tried this one: find|xargs -n 1 echo This also leaked at around the same rate. Then I tried the following: COUNTER=