jsillup

steinsel.tuvpn.com|LU

neoinx.net|ZA sihnon.net|UK ************************ logicsouth.com|US

@doug2h: I was also getting the I/O Error messages at startup that you report. They stopped after I set "bt.determine_encoded_rate_for_streamables" False in Advanced Options.

I previously reported that files in finished torrent directories get ".!ut" appended to their names whenever I start µTorrent version 2.1 despite all the files remaining marked 100% complete on the µTorrent Files tab (I have "Append .!ut to incomplete files when downloading" option enabled). This always happens when a multiple file torrent contains at least one video file. Re-checking the torrent will remove the unnecessary ".!ut" appendages but also clears the torrent's "Completed On" date! Momentarily starting the affected torrent(s) removes ".!ut" from file names without disturbing "Completed On". I neglected to mention that "Error opening..." messages would sometimes also be logged at startup. I reported in the same post that if I add a torrent I had previously downloaded and removed from my Finished list then re-check it, the Done percentage indicator always stops at around 99.5%. I have to re-check a second time for the torrent to be indicated as 100% Done. Today I found that these problems are a result of Advanced option "bt.determine_encoded_rate_for_streamables" being set to its default value of True. Setting this option False resulted in no more problems for me whenever I start µTorrent version 2.1. I am especially glad that re-checking multi-file finished torrents containing video files no longer clears the "Completed On" date. I am running Windows 7 x64 and have made sure that the directory in which my finished torrent files are stored (on partition D) is not being indexed.

Version 18936 crashes if "Resolve IPs" is selected in Peers tab despite fresh Settings.dat, no Flags.bmp or Flags.conf: http://www.mediafire.com/file/azylzzemmkj/18936-utorrent.8090.dmp Plus a false "Drop files to share" tab appears on top of the "General" tab when µTorrent starts but disappears as soon as another vailid tab is selected. I'm running Win7 x64

I've also seen some peers in the Peers tab list colored blue, but only when a torrent is starting. After the torrent runs for a few seconds blue colored peers change to black and seem to remain so. I also have the previously posted problem where files in finished torrent directories get ".!ut" appended to their names whenever I start µTorrent version 2.1 despite the fact that the files all remain marked 100% complete on the µTorrent Files tab. This only seems to happen when a multiple file torrent contains at least one video file. Re-checking the torrent will remove the unnecessary ".!ut" appendages but also clears the torrent's "Completed On" date! Momentarily starting the affected torrent(s) removes ".!ut" from file names without disturbing "Completed On" so that is what I am doing. Another oddity is if I add a torrent that I had previously downloaded and removed from my Finished list then re-check it, the Done percentage indicator always stops at around 99.5%. I have to re-check a second time for the torrent to be indicated as 100% Done. I am running Win7 x64 and have made sure that the directory in which my finished torrent files are stored (on partition D) is not being indexed.

FYI, I am running Windows 7 x64 and am not experiencing any problem with uTorrent obeying a "Kill Pocess" command in Process Explorer (or Task Manager) or being reported as running after I close the program.

philonline.com|PH

I also experienced the crash reported by @AGE after updating from 1.8.3 beta 15358 to 15520 under Vista Ultimate x64 SP1: Problem Event Name: APPCRASH Application Name: utorrent-1.8.3-beta-15520.upx.exe Application Version: 1.8.3.15520 Application Timestamp: 4a175313 Fault Module Name: msvcrt.dll Fault Module Version: 7.0.6001.18000 Fault Module Timestamp: 4791a727 Exception Code: 80000001 Exception Offset: 00009a32 OS Version: 6.0.6001.2.1.0.256.1 Locale ID: 1033 Additional Information 1: fd00 Additional Information 2: ea6f5fe8924aaa756324d57f87834160 Additional Information 3: fd00 Additional Information 4: ea6f5fe8924aaa756324d57f87834160 I tried deleting my settings directory and reinstalling without success. Then I tried deleting all references to utorrent in the registry. After doing that 15520 installed successfully and is now running well for me.

Upload speed is VERY slow for me with 1.9 alpha 13485/13550 under Vista Ultimate SP1 32-bit, less than half of the 1MB/s I reliably achieve with 1.8.1, plus 13550 consumes almost all CPU speed which appears to make it freeze as reported earlier. No improvement for me turning off uTP and/or disabling cFosSpeed with 1.9. 13550 logs are here: http://rapidshare.de/files/41007944/uT19_logs.ZIP

@jeps92: UPnP works fine for me in Build 12549, both from my main PC running Vista Ultimate x86 (32 bit) and my laptop running Vista Ultimate x64 with wired and wireless connections respectively into an AVM FRITZ!Box WLAN 3270 router. Are you sure your firewall is letting µTorrent "talk" to your router? Turn on "Log UPnP messages" in Verbose Logging to verify.

@Lim-Dul, You're too late, Uncle Alus found a work around already. But if you still want to force the crash with Build 12323, try disabling your NIC while µTorrent is running with UPnP port mapping enabled.

@alus, I found an easy way to reproduce the "Vista bug", see your email for details. Regards, Joe

@alus, I did more "Vista bug" testing, check your email for my results. Crash dump is here: http://rapidshare.de/files/40560506/12465-utorrent.feb8.zip Regards, Joe

@alus, I did more "Vista bug" investigation (using 1.8.1 Beta build 12323): UPnP PortForward utility confirms that µTorrent correctly forwards the TCP and UDP port µTorrent is listening on whenever it is started (including when it crashes after a router reboot) and releases them when it exits normally. If I use PortForward to set up the forwards after rebooting my router, then start µTorrent it will not crash. -> If I delete "resume.dat" and "resume.dat.old" then reboot my router and start µTorrent it will not crash! <- Similarly, it I stop all torrent activity and set "bt.scrape_stopped" false before exiting µTorrent, then reboot my router and start µTorrent it will not crash. So for me the crash only happens on the first start of µTorrent after rebooting my router when there is torrent activity (even just tracker scraping) ready to be started immediately! There seems to be something µTorrent should wait for that Vista has to do (or finish doing) after the initial UPnP port forwards before starting torrent activity. Regards, Joe

@alus, I did more crash testing, check your email for my results. Regards, Joe

@alus, "Vista bug" crash seems to start at 1.8 Beta Build 7211, I cannot make Build 7210 or earlier crash. Regards, Joe

@alus, Neither of the test builds you sent me crash. Both open ports in my router with UPnP. But neither connects to any peers, even after deleting my µTorrent firewall rule and making a new one. UPnP message logging says that they cannot get external IP, if that matters. Regards, Joe

@alus, For me the crash starts at Build 7400 of the 1.8 versions in the alpha directory you sent me via email. Builds I tried above 7400 are OK. Any build after 7400 that I tried crashes. From what I can tell the problem started in 1.8 alpha 7400.

@alus, This build of µTorrent runs without any problem when started with UPnP port mapping enabled after my router reboots: utorrent-1.8-alpha-7399.exe But this build crashes the first time started with UPnP on after my router reboots: utorrent-1.8-alpha-7400.exe Crash dump is here: http://rapidshare.de/files/40531742/7398-utorrent.b34b.dmp Vista problem report: Problem Event Name: APPCRASH Application Name: uTorrent.exe Application Version: 1.8.0.7398 Application Timestamp: 47803b85 Fault Module Name: hnetcfg.dll_unloaded Fault Module Version: 0.0.0.0 Fault Module Timestamp: 4791a6c2 Exception Code: c0000005 Exception Offset: 714ec7fa OS Version: 6.0.6001.2.1.0.256.1 Locale ID: 1033 Additional Information 1: 0e02 Additional Information 2: b21b56b606e7544720668ce364087082 Additional Information 3: ed9f Additional Information 4: 2119b83e2e89962308d1cebda6adacd3 I see no difference between logged UPnP messages in either builds, and the router sets the UPnP port forwards correctly for both builds. Note that the crash only happens the first time Build 7400 is started after a router reboot, restarts after that crash run without problem until I reboot my router again. AVM FRITZ!Box routers are popular in Germany and the one I just got is their best non-VoIP 300Mbit WLAN model, but I doubt you can get it in the USA to use for debug so I will do whatever I can to help you from here. Best Regards, Joe

Hello @Alus, As I said, I can reliably reproduce this "Vista bug" crash simply by rebooting my router then starting µTorrent with UPnP port mapping enabled, so if there is anything further I can do to help you debug I will be happy to help. Regards, Joe

I just finished setting up a FRITZ!Box WLAN 3270 Router which supports UPnP (my previous router did not) so I enabled UPnP port mapping in µTorrent (v1.8.1 b12323) and got a crash! I downloaded the uncompressed version, tried again, and got another crash: http://rapidshare.de/files/40527994/12323-utorrent.b096.dmp With UPnP off and manual port forwarding in the router all is well. But since the first two crashes I can delete the manual port forwards in the router, enable UPnP in µTorrent, and it works fine. However if I reboot the router µTorrent will crash again! Only the first attempt at port forwarding with UPnP after the router boots up causes the crash, but this is perfectly reproducible. If more dumps or other information will help debug please let me know. I am running Vista Ultimate x86 SP1, so perhaps this is the famous "Vista bug"? Problem Event Name: APPCRASH Application Name: utorrent.exe Application Version: 1.8.1.12323 Application Timestamp: 48d6d81e Fault Module Name: hnetcfg.dll_unloaded Fault Module Version: 0.0.0.0 Fault Module Timestamp: 4791a6c2 Exception Code: c0000005 Exception Offset: 702ac7fa OS Version: 6.0.6001.2.1.0.256.1 Locale ID: 1033 Additional Information 1: 0e02 Additional Information 2: b21b56b606e7544720668ce364087082 Additional Information 3: ed9f Additional Information 4: 2119b83e2e89962308d1cebda6adacd3 Best Regards, Joe

tr.net|TR