Enden Posted September 5, 2016 Report Share Posted September 5, 2016 I've a workstation with 16 GB DDR4 that's running 24/7, but for some reason, uTorrent is using almost all the memory. If I restart uTorrent, memory usage drops to 4 GB? Link to comment Share on other sites More sharing options...
DreadWingKnight Posted September 5, 2016 Report Share Posted September 5, 2016 uTorrent can't be using all the memory, it's a 32-bit process and will crash at 2GB of memory usage. It's more likely windows disk cache stupidity. Link to comment Share on other sites More sharing options...
Enden Posted September 6, 2016 Author Report Share Posted September 6, 2016 Do you have any suggestions for a possible solution? It's obviously an issue that's related to uTorrent. I'm using the latest version of Windows 10 Professional, 64-bit - and the latest stable version of uTorrent. Link to comment Share on other sites More sharing options...
Enden Posted September 12, 2016 Author Report Share Posted September 12, 2016 Memory usage dropped from 99% (!) to 19% after closing uTorrent. Link to comment Share on other sites More sharing options...
gjm Posted September 24, 2016 Report Share Posted September 24, 2016 What size page file are you using? (Assuming W10 uses a pagefile - I've treated it liek the plague and stayed well away!) Edit: Definite memory leak issue. Watching processes in Windows Task manager, I can see uTorrent memory utilisation continually increasing at the rate of about 4k per second. My system details from my post re: uTorrent stops... W7 Pro SP1 64 bit uTorrent 3.4.9 Beta (build 42598) 32 bit Actrix (www.actrix.co.nz) BitDefender Further edit: Screen shots supporting the case for continually incrementing memory usage. No activities other than screen shotting took place during this time; time period is 6.10 through 6.26; the only live application was uTorrent; uTorrent was 'empty' - no downloads or uploads were present or in progress. Despite this, memory utilisation continued to climb as shown. The final shot shows utilisation after a uTorrent shutdown and start (6.27). Following the uTorrent restart, it's memory utilisation is around 14700kb. This immediately starts to climb at the rate of around 4kb/s. Link to comment Share on other sites More sharing options...
gjm Posted September 25, 2016 Report Share Posted September 25, 2016 I've updated to Build 42604 - memory utilisation issue unchanged. Edit: I've completed uninstalled uTorrent, including all settings. Clean reinstall of build 42604. I've not added any torrents, upload or download, but with the application theoretically idle, memory utilisation is still increasing at a rate of 4k+ per second. Looks like there's a leak in there somewhere. Link to comment Share on other sites More sharing options...
DreadWingKnight Posted September 25, 2016 Report Share Posted September 25, 2016 The "leak" is in the windows disk cache subsystem. Link to comment Share on other sites More sharing options...
gjm Posted September 26, 2016 Report Share Posted September 26, 2016 4 hours ago, DreadWingKnight said: The "leak" is in the windows disk cache subsystem. So... Is it an implementation issue, an underlying Windows issue exposed by the uTorrent application, write-cache configuration, or something else? Is there anything you can recommend I/we can do to prevent it? Link to comment Share on other sites More sharing options...
Enden Posted September 28, 2016 Author Report Share Posted September 28, 2016 - Link to comment Share on other sites More sharing options...
Enden Posted October 25, 2016 Author Report Share Posted October 25, 2016 The issue seems to be explained pretty well in the following thread; Link to comment Share on other sites More sharing options...
Enden Posted October 25, 2016 Author Report Share Posted October 25, 2016 Adding an option to automatically restart utorrent after xx hours, should be easy to implement, and work as a temporary fix. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.