Jump to content

eliot_cougar

Established Members
  • Posts

    47
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by eliot_cougar

  1. Finally found the culprit to be the new ReFS.sys driver... It has been updated in KB5003690 to the version 10.0.19041.1081... I've installed the update on July 3rd, and that's when the weekly memory leaks started... It happens every week at the same time, right after Windows performs its scheduled maintenance, and creates a restore point... Surprisingly, I don't see this issue on a different machine with a similar ReFS volume... 7 effin' gigabytes!.. The registry change to uTorrent did help with the RAM usage a little bit, but the main problem was not that... UPDATE after one month: The ReFS.sys driver has been slightly updated, but the issue is still present, and I don't see it reported by anyone else (not many people use it, I guess)... I was able to automate the preventive measures by triggering "Free Working Set" command (EmptyStandbyList.exe) when the amount of free RAM drops below 1gig... Somehow that lets the ReFS driver release all the RAM it took...
  2. Looks like this is exactly my issue, at least partially... I have many huge 4K torrents active, and according to RamMap it quickly leads to up to 4 gigabytes of RAM used in the Mapped File category, especially if the upload rate is high... I'm trying to use this advice right now to see if it helps... Also, there seems to be a different source of leaks since I've updated to Windows 10 21H1... I ran out of memory this morning without uTorrent running... Happened for the second time this morning...
  3. I have no idea what is going on... Maybe it's the latest Windows 10 update... I reverted back to 45988... I restart uTorrent at 22:25 with your settings that is not too different from mine, and let it run for a while with almost constant 3MB/s upload with 74 torrents active (not all of them actively uploading)... According to Task Manager uTorrent.exe has only about 150MB of memory allocated the whole time... 35 minutes later I have 2 gigabytes of free RAM less... I close uTorrent, and that releases 3.2 gigabytes of RAM... I don't know what has been using all that RAM, but it is not displayed anywhere in the Task Manager... Pagefile usage hasn't been changing much - it seems to only go up when there's less than 4GB free RAM... Filesystem cache?..
  4. Update: version 46038 (LAA version too) still leaks memory like crazy... I even tried disabling BTT feature with no effect... Maybe it's because I have 70+ active uploads?.. The leaks seems to be proportional to the upload speed... Not sure if it's been this bad before version 46010 - I do see some strange downward trends in the old RAM and pagefile usage graphs... Not as steep as is is now... There was a Windows update as well, though...
  5. I can confirm the memory leak... uTorrent had an auto-update to 46010 yesterday, and overnight my machine ran out of memory, and the pagefile grew to 20+ gigabytes... Everything halted to a stop, and I had to reboot... Right now it leaks memory at approximately 50MB per minute... The leak stops if I close uTorrent... Cache settings don't have any effect on that... Auto-update doesn't find any new versions, but I have version 46038 on another machine... I'm gonna try to update manually and see if it helps...
  6. Oh, yes... This bug is very annoying... I guess it was there since first 3.0 alpha, and it is still there... However it happens only with some torrents, not all... It happens almost all the time with big torrents which contain long list of files (e.g. All seasons of some TV series in one torrent)...
  7. Bug: bt.transp_disposition have been defaulted to 15 somehow...
  8. It took me 2 minutes to find this option even if I use uTorrent for 2 years... What is the meaning to have two very closly named options in two settings tabs?.. PS: The option says: When adding torrents show that window... Why doesn't it do so?.. That's problem - inconsistence between expectancy and fact...
  9. Bandwidth limiting: "Apply rate limit to uTP connections" state is not remembered - Check it, press OK/Apply, Open the window again, still unchecked... Silent torrent adding: uTorrent does not open Add Torrent dialog no matter what is the state of the option "Show a window that displays the files inside the torrent"... Upgraded using the auto-update... I expect fixed revision soon... Very soon...
  10. Ofcourse it's enabled... I'm talking about this bug: http://forum.utorrent.com/viewtopic.php?pid=469446#p469446 It's Windows-specific, if you try to get FQDN for your own machine like this: socket.gethostbyaddr('your.own.ip.addr') or this socket.getfqdn('your.own.ip.addr') Windows will return your NETBIOS name instead... We have found that you have to set additional flag DNS_QUERY_WIRE_ONLY to force Windows to bypass cache and do real DNS request... Greg has wrote some advanced code to make that work, but it still doesn't seem to be included in the latest revisions...
  11. I still don't see the BEP22 fix Greg Hazel has made long ago... It prevents Windows to use its DNS cache system which returns NETBIOS name on FQDN request... (Stupid Win)
  12. I feel a bit of misunderstanding here... A lot of people DO NOT understand what the overhead is... I'm sure most of them think that overhead should be ZERO in the very ideal case, and any high number means simply "uTorrent behaves bad and can't use the full potential of the connection"... It'll be better to hide actual overhead numbers somewhere and not display them in the main window... UPD: The simple rule: NEVER set your UL limit less than 10% of your DL limit and vice versa...
  13. And once again, do you have any downloads active?.. Downloads DO generate upload overhead and vice versa... (Oh my...)
  14. Ofcourse I know that... You just missed what I was trying to say... To make measurements precise enough uTP has to keep DATA packets smaller... But that's not good if you make EVERY AND ALL data packets smaller to do those measurements... Read my post again, keep in ming that those I call "measurement packets" are actually DATA packets small enough to do precise delay measurements and all other packets are DATA packets large enough (MTU) to make overhead smaller... PS: This forum is strange, Where's "quote" button?.. Where's BBcode editor or RichText editor?.. I have only nacked textfield to write my post and I have to do all BBCode formatting manually...
  15. How many delay samples per second does uTP need to do it's congestion control efficiently... Does it really need delay measurements for every packet?.. Maybe it can send "small" (measurement) packets only sometimes (e.g. every 10th or every second) and send MTU-sized packets most of the time?.. Keyword: sampling interval ISPs, along with online gamers and VoIP users, are really angry on current implementation of uTP... Our ISP started to block uTP traffic after recieving complaints (high ping and packet loss) from online gamers...
  16. BEP22 still behaves the same for me, using Netbios name but not DNS name... What was fixed then?..
  17. It may be useful for small networks with a couple of different IP ranges, but what about big ISPs with much more subnets/ip ranges?.. How many users are really that technically educated to know how to customize that "list of local IP ranges" and take benefits?.. The simpliest solution I imagine: You have local tracker - right click - mark as local... Then the client treats all peers reported via that tracker as local and loose speed cap for them... You can even have an option in preferences, text field to enter the address of your local tracker... BEP22 seems good, but I've heard that not all users can make SRV DNS requests, or something like that, I'm not sure, I've never had such problems... And simple A/AAAA record is good too... Let's make an agreement to always treat http: // retracker.local / announce as local tracker... Some ISPs are using that already, anyway... And it works well... It's better than multicast-based LPD we have at the moment... The last thing we must think about is announcing "private" torrents on local trackers: allow or deny?.. Speed and traffic internalization or supporting stupid concerns about ratings, UL/DL ratios, "top-seeder" statuses and all such pointless crap we have on "private" torrents now...
  18. I would like to see local tracker discovery and local peer prioritization... And ability to discriminate local trackers (containing local peers) to make uTorrent set flag L to peers obtained from them and release speed cap... Some trackers use retracker.local/announce as universal local retracker, ISPs just add it to DNS, and then it works... BEP22 would be better if it will work... Not sure if local retracker should be added to "private" torrents, but it better be added... Most of the trackers are "private" (so, we have less probability to find fast local peer if we don't), and user can always add local retracker manually, anyway... Restricting local retracker usage for "private" torrents does not have sense... Option to "always announce to local trackers" to make it possible for local peers to download torrent from local network even if all local seeds have high U/D ratio and "Queued Seed" status for that torrent... Many users have 200+ torrents, but only a bunch of them are announced... It lowers the probability to find local peer for other local peers... If torrent have several main trackers and local retracker (obtained through BEP22 or retracker.local) it would be nice if "Queued Seed" torents will be announced to local tracker, but not to the main trackers (if U/D ratio is high)... I'm just trying to imagine how to increase local traffic flow and decrease ISP's external link congestion...
×
×
  • Create New...