I've been running a `wget' process for probably a week now in the background on my Linux box. It's taking up roughly 184MB of memory total (RAM + swap), and was wondering if this was a possible memory leak issue (as with 1.5.x, I forget the version exactly), or if this was a function of some data that wget is storing internally (perhaps the log file itself is loaded into RAM and not just dumped to disk--that's my best guess). If the latter, is there an option for wget that will tell it to use less memory, or cut itself off after a certain point, or some such thing? It's reasonable to expect that 184 megs would be used after a week on a cable modem mirroring a site, but I'd like to know what all that RAM is doing! (Googling `wget memory' references an old leak from 2001, and `wget 1.8.2 memory' and variations on that theme render no useful links.)

Thanks in advance for your time and reply.

Be well,
Michael

Check out valgrind its an excellent program for detecting memory leaks and stuff.

Been there, done that. I also see an apparant memory leak in wget, at version 10.1. I had it running for 4 days and my machine had 99% of the physical memory (256MB) consumed. There was 1GB of swap configured, 600MB of it was in use! I filed a valgrind report but filing wget bug reports is like lobbing messages into a black hole. Can anyone shed any light please?

-Andrew Marlow