Simon100

RC6 - Translation file won't download

I'm running Windows 7 x64 & Windows 2008 Server R2 x64 Standard Edition as I no longer have anything w/ 4GB or less of memory. Edit (Ultima): Snipped unnecessary quote...

Just did a test on a 1.5Mbps/384 WAN w/ virtually no disk activity and uTorrent STILL froze. It appears, connections related as a leading factor.... sometimes it'll freeze with no torrents running. If I have a couple hundred opened and I changed ports, uTorrent freezes, even though there was negligible disk activity.

One of the newest "feature" in the current RC it seems that whenever I change Preferences, do Network tests (the Green Checkmark) or change the speeds (right-click the boxes next to Checkmark), uTorrent RC2 22732 seems to FREEZE, then Logger shows several Hang Diagnostics. Is anyone else having similar experience??

# of upload slots / torrent is missing on latest 22328, changelog does not give a reason

If you zoom into the torrent list & the screen refreshes, a large portion of right-hand screen is grayed-out. You must un-zoom and wait for it to refresh (or manually refresh) before screen goes back to normal.

Although I use the MiniUI on the iPhone to "fine tune" torrents (or is there something better?), but I still prefer using WebUI on iPhone Safari to quickly focus/check on torrents. uTorrent v2.0.4 + WebUI v0.371, was great, I can focus/enlarge the display without issues, BUT uTorrent v2.0.4 + WebUI v0.380, the display turns GRAY when I enlarge the display. Can WebUI use the previous method for screen draws on iPhone's Safari as to NOT GRAY out most of DISPLAY area? Thanks...

You have to disable uTP to eliminate "saw tooth effect" in lower speed wan connections or connections you over use, eg latency fluctuates constantly :-(

I had originally thought latest 2.2 Griffin would fix the "hands/freezes" but it still happens "alot", or too often than it should. Older releases that now have "security defects" did not have this issue. I believe it started happening more often when the "security patch" build was made available.

Using build 22007, I'm wondering why are there so many "Hang diagnostics" & "Hang reported successfully" statements in the logs? It seems every time I make a change in preferences or "sometimes" when set the bandwidth (right click bottom status, left of green check mark), uTorrent freezes for a few seconds and then act normally, whiling loging "Hang diagnostics"... This was also the case with v2.0.4 (build 21586)..

21882 does not move torrents in "incomplete torrents directory" to "completed torrents directory" after finishing. Only the *.torrent file is moved. v2.0.4 was ok

I have a server which runs v2.0.4 build 21586 for extended periods of time, and I notice it slowing down to crawl after a couple weeks. Regular browsing is not affected, only if I exit and restart uTorrent does my speed go back to normal. Is anyone else noticing this? Memory remains contant at about 20MBytes and running on a recycled Windows 2008 Server.

Did some more testing w/ v2.04 21586. I HAD disabled bandwidth management uTP in v2.0.3 because it was slowing the torrents. It was a long running, 10GB torrent. Anyhow, I enabled bandwidth management, which made it run faster again, and after about an hour or so, I again diabled bandwidth managent and everything is fine now. I'm just wondering as to why I must start my torrents w/ bandwidth management enabled, & after awhile disable it to have good torrent performance which almost saturates my connection? Can others replicate this?

I've just upgraded to v2.04 21586 and it seems ALOT slower than the previous v2.0.3 20664. I can't seem to connect to as many peers. I fired up v2.0.3 and everything is fine.

I just don't think it's the job of uTorrent to perform "Traffic Management"/"Taffic Cap". Virtually all the good, yet free router software manage traffic extremely well. Limiting traffic based on one of several critera, and even shutting down a connection once you've reached the "total" cap is much more reliable than the transfer cap in uTorrent (as it ONLY counts uTorrent's data).

I can't seem to get uTP to work right. Our ISP do not throttle or have CAPs as I've always gotten full speed, but uTP seems to work on the ISPs behalf (and for their benefits) by throttling my d/l speed even though it is in the middle of the night and I should be getting full speed (the speed I an paying). I started several torrents but still getting low speeds. I'm just curious as to why use it or turn it ON by default when it has such high overheads and lousy speeds. My router seems to shape my traffic MUCH better than the uTP. I've used a simple Tomato, OpenWRT, and pfsense, etc... and they all seem to prioritize and de-prioritize traffic consistently and almost instantly (shown by the bandwidth graphs).... and fine tuning them is easy. I hope you'll consider "disabling uTP" as the default in future releases..

"bt.enable.tracker" set to true on server created torrent on server. Trackers field was left blank to allow local peer discovery. grabbed torrent on local lan connected computer. started huge transfer & was unable to set "Maximum Download & Upload rates" Those settings are IGNORED Apparently, uTorrent does not honor locally connected LAN connected computer rates. Being UNABLE to set it globally by havng the lan transfers ignore it globally is ideal as local transfers can be hundreds of times faster than those thru the Internet, BUT utorrent should allow Max DN/UL be set INDIVIDUALLY by torrent even if they are Local peers. Can someone verify this issue with v2.0.2?

Magnet D/L does not abide by the Preferences|Directories for build 18973. In other words, magnet d/l should put the magnet-fetched DHT-based torrent file in the "New downloads/store new torrents Folder" & move the completed D/L & torrents to the "Completed/finished job" folder.

I'm on vacation now. For those also getting "Reporting hang diagnostic information.", can you follow the instructions Firon gave me in post #43 and upload your diagnostic dumps info to him for analysis.... Thanx..

Hi, Here's what the logger says, which didn't crash under Windows 2008 server, server is more reliable it seems and utorrent only freezes for for a minute: [2010-03-31 15:29:40] NOTE: Settings file found in directory of executable; using that. [2010-03-31 15:29:40] Loaded ipfilter.dat (0 entries) [2010-03-31 15:29:41] *** Starting Diagnostic thread *** [2010-03-31 15:29:41] IPv6 is installed [2010-03-31 15:29:41] Got Teredo Address: 2001:0:4137:9e74:1c6b:da64:b4cf:e6a8 [2010-03-31 15:29:51] Error opening Windows firewall: 0x80070005 Access is denied. [2010-03-31 15:40:11] Reporting hang diagnostic information. [2010-03-31 15:40:11] http://www.utorrent.com/report_problem.php?v=67324305&h=_to1KvBTwogHAqzA&w=1DB00106&p=hung&s=0&li=n:1:0:main:main:0&wm=393670:514:0:655410:617249,393670:15:0:0:617202,328220:15:0:0:617187,393670:513:1:655410:617187,393670:512:0:655410:617187,393670:512:0:655411:617093,656128:15:0:0:617015,m:275:3603988:0:617000,393670:512:0:983092:616968,393670:512:0:1376308:616875,393670:512:0:917559:616688,197142:512:0:20513003:616563,328220:675:0:0:616407,197142:512:0:19529973:616407,328220:512:0:852017:616313,656128:15:0:0:616001,m:275:3603988:0:615986,328220:15:0:0:615705,1114736:15:0:0:615705,328220:512:0:393267:615705 [2010-03-31 15:40:18] Hang reported successfully: [2010-03-31 15:40:18] http://www.utorrent.com/report_problem.php?v=67324305&h=_to1KvBTwogHAqzA&w=1DB00106&p=hung&s=0&li=n:1:0:main:main:0&wm=393670:514:0:655410:617249,393670:15:0:0:617202,328220:15:0:0:617187,393670:513:1:655410:617187,393670:512:0:655410:617187,393670:512:0:655411:617093,656128:15:0:0:617015,m:275:3603988:0:617000,393670:512:0:983092:616968,393670:512:0:1376308:616875,393670:512:0:917559:616688,197142:512:0:20513003:616563,328220:675:0:0:616407,197142:512:0:19529973:616407,328220:512:0:852017:616313,656128:15:0:0:616001,m:275:3603988:0:615986,328220:15:0:0:615705,1114736:15:0:0:615705,328220:512:0:393267:615705 [2010-03-31 15:40:21] http://www.utorrent.com/report_problem.php?v=67324305&h=_to1KvBTwogHAqzA&w=1DB00106&p=unhung [2010-03-31 15:40:21] Hang reported successfully: [2010-03-31 15:40:21] http://www.utorrent.com/report_problem.php?v=67324305&h=_to1KvBTwogHAqzA&w=1DB00106&p=unhung It happened as soon as I hit "Random port". Try downloading a couple of torrents for a while that has alot of client/seeds, then hit Random port, it should then freeze, possibly cleaning up the already connected ports??? I've tried it on separate systems and it still occurs. Strange, no one can reproduce it? -Simon

now updated to µTorrent 2.0.1 RC1 (build 18833) on win7 64-bit. Whenever I click "Random port" button under Connection, Listening port while a torrent is running, uTorrent Freezes & sometimes crashes. In previous version, Under logger, it reported "Hang diagnostics information w/ Hang reported successfully... statements". I also tried build build 18833 on a win 2008 64-bit machine & it also happens..

Everything d/l OK on this site. Must be your connection/location. Difference part of the world will block certain sites.

using 2.0 build 18620 w/ uPnP enabled on win7 64-bit. Before starting torrents, I click "Random port" button under Connection, Listening port. Check router, saw uPnP opened proper ports, both tcp & udp of port opened. Ran torrents for couple hours, # of conn is about 2500-3000. As soon as I click "Random port" button in utorrent, utorrent hangs for about 10 seconds, and then all is fine. Under logger, it reported "Hang diagnostics information w/ Hang reported successfully... statements". Just wondering if this is a known issue. I also tried this on a win7 32-bit machine using a script via the webui to randomize ports every 2 hours, this issue seems to still affect it. Should I shorten the time to Randomize ports, say every hour or 30 minutes, so as to not cause utorrent 2.0 build 18620 to freeze each time this happens...???? thanx....

Hi rafi, It didn't help, I suspect those clients are hard coded to refuse to or only transfer very little with clients versions that they do not recognize. I seem to remember something similar happening on torrents from Asia when v1.8.x was released. I'm just hoping those other clients will be updated, and or also have uTP capabilities so as to connect efficiently with others. I'm almost certain that Xunlei and BitComet will only connect fast when connected to themselves. I've noticed that BitComet is vanishing rather quicly from Asia, replaced by Xunlei. Xunlei is notorious for sucking all your bandwith and very quickly sharing everything you have with other Xunlei users, but at least with 1.8.5 I can eventually finish, albeit very slowly. I've tried everything mentioned in earlier posts as well.

I'm just wondering why Xunlei and BitComet refuses to exchange packets with uTorrent 2.0 (17920) on a torrent with many/mostly Xunlei and BittComet peers, no seeds. I mean exchanged very few packets or not connect at all. Availability was about 2.7. After nearly a week, transferred at a snail's pace. Stopped torrent, replaced utorrent.exe with 1.85 (17414). Transfer immediately picked up and it finished in a day and a half. Is there compatibility issues with other clients?