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
On 03 October 2007 14:39, wimxa wrote:
> Dave,
>
> Nope, this one is called Webroot Spy Sweeper (if it is the problem with it).
It almost certainly is! Morgan Gangwere mentioned that software before but
I forgot to add it to TBLODA; it's definitely going on now.
http://cygwin.com/ml/cygwin/2
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.
--
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
On 03 October 2007 13:38, wimxa wrote:
> 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.
Is it one of the ones listed on TBLODA at
http://cygwin.c
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
On 03 October 2007 05:31, Christopher Faylor wrote:
> On Wed, Oct 03, 2007 at 04:20:18AM +, Lewis Hyatt wrote:
>>> Anyway, can I ask you to do this yourself - just do the last test:
>>>
>>> COUNTER=1
>>> while [ $COUNTER -lt 123456 ]; do (echo $COUNTER); let
>>> COUNTER=$COUNTER+1; done
>>>
On Wed, Oct 03, 2007 at 04:20:18AM +, Lewis Hyatt wrote:
>> Anyway, can I ask you to do this yourself - just do the last test:
>>
>> COUNTER=1
>> while [ $COUNTER -lt 123456 ]; do (echo $COUNTER); let COUNTER=$COUNTER+1;
>> done
>>
>> and wait a little (couple of minutes). If necessary, repe
> Anyway, can I ask you to do this yourself - just do the last test:
>
> COUNTER=1
> while [ $COUNTER -lt 123456 ]; do (echo $COUNTER); let COUNTER=$COUNTER+1;
> done
>
> and wait a little (couple of minutes). If necessary, repeat it until your
> memory drops to 10-20 MB range and your HDD shou
> 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.
wimxa wrote:
Try executing:
find -exec echo {} \;
Simple command. This one, however, leaks at about 5kB/s. I tried the
following:
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 aut
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=
12 matches
Mail list logo
