to Guest2: That really doesn't sound like a memory leak. During the course of normal use, the amount of available memory will go up and down. The amount stated above is within normal operating parameters.
However, what is *NOT* normal is when someone starts with 512 MB and within roughly 1 hour they are down to under 50. If all they have open is 1 torrent and IE, that indicates a major memory leak since according to TaskManager most of the RAM is unaccounted for. It's just listed in System Cache. For some reason BT is not recycling the RAM it uses. But why is it only happening to some people? It doesn't seem to matter which version is being used. There have been people saying that they are only seeing it in the latest build, and others saying this issue has been going on ever since they first started using BT. Others say that it was fixed in one version or another. Sometimes it comes back and sometimes it doesn't.
What the hell is going on??? Is there some Windows issue at play here? I am assuming that everyone having problems is on some variation of Windows, since I haven't seen anyone mention *nix problems.
One thing I have noticed for me is that opening Winamp seems to exacerbate problems. The memory leak is an ongoing issue, but when Winamp is added into the mix, system slowdown starts to occur after a short period. If Winamp is not opened, the memory just goes down to around 100 and hovers in that area, and if it gets below a certain point Windows frees up a bit from the cache. But slowdown/freezing is never an issue. Just an observation I had. Might have nothing whatsoever to do with BT, except this only happens when i have BT and Winamp open simultaneously.
BTW, I am on a P4 2.66 Ghz(Bus Speed=533)/ 512 DDR SDRAM(PC2700), 80GB SATA HD @ 7200rpm. 128MB nVidia GeForce FX 5200
OS=Windows XP Home fully patched (or at least the MS equivalent of patched
)
AV=McAfee VirusScan 8.0
FW=Sygate Firewall Pro 5.5