Ismelda Posted August 28, 2011 Report Share Posted August 28, 2011 I don't know how this happens but the longer µtorrent runs the less Memory available I have. This ends up in slowing the whole computer and forces me to close µtorrent which immediately liberate all the used memory. I am using last version of µtorrent with windows 7 and have 8Gb of RAM.I also noticed that the RAM usage can drop down by itself when a torrent finished downloading but for large torrent which take days to download the strain on the ram is constant and can't drop down...So this is not really a bug per se but more an issue raised by the usage of µtorrent like a memory leak. Link to comment Share on other sites More sharing options...
DreadWingKnight Posted August 28, 2011 Report Share Posted August 28, 2011 If the uTorrent.exe process isn't the one eating the ram, it's the windows disk cache being stupid AGAIN. Link to comment Share on other sites More sharing options...
Ismelda Posted August 29, 2011 Author Report Share Posted August 29, 2011 Indeed the µTorrent process itself is not acting weird like using all CPU or being extremely bloated in Memory usage. It is just the available physical memory that is eaten away until there is nothing left to use for other programs.On very rapid torrents (3Mb/s to 10Mb/s download) I thought it was the system way of dealing with the read/write processes so that a steady flux will access the HD, thus ensuring best performance, but even if I have only slow downloads (less than 1Mb/s download) the physical memory ends up being all dedicated to the torrents. Link to comment Share on other sites More sharing options...
pascal4 Posted September 1, 2011 Report Share Posted September 1, 2011 Windows 7 64-bit has a stupid cache bug, and I haven't yet seen it on 32-bit but then again I haven't been that long on it. It used to happen with Azureus and other Java based apps that use extensive memory, Firefox 3 as well. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.