The MAZZTer

Members
  • Content Count

    8
  • Joined

  • Last visited

Community Reputation

0 Neutral

About The MAZZTer

  • Rank
    Newbie
  1. The problem I described here: http://forum.utorrent.com/search.php?action=show_user_posts&user_id=550940 is still occurring. Due to major ISPs now cracking down on certain "content" (see: https://www.google.com/webhp#q=isps%20july%201st), it is now more important than ever for users to use programs like Tor to stay anonymous on the Internet. uTorrent currently makes this difficult due to this bug. I will post a proper thread in the bug reports forum to make this more visible...
  2. The private tracker works fine if the proxy is turned off. uTorrent never even queries the tracker since the tracker url becomes corrupted, as I said... even if you specify a URL with the private session id stripped off (as I did) the crash still occurs, so it's happening before processing the tracker reply most likely (the error messages utorrent spit out suggest it fails to establish an SSL session, maybe due to more corrupted memory). So it is clearly either due to Tor or due to uTorrent. Tor transparently wraps connections and using Tor with torrent files from public torrents works fine so I doubt it plays a factor. As a programmer I speculate that in some code path relating to proxies, the memory space holding the url and some SSL session data, and perhaps part of the stack or heap (or something that eventually causes the crash) is overwritten by accident when utorrent goes to connect to it. I normally use Tor directly so I did not think of using Privoxy as a workaround, I'll try that in the meantime, thanks. It might also explain why this issue hasn't been widely reported, out-of-the-box you use Privoxy with Tor. [Edit: Nope, I forgot Privoxy was cut out and replaced with Polipo I think. I'll try that.] [Edit: Boo, looks like Polipo might not handle CONNECT, or at least the FAQ indicates it's for HTTP traffic only. I'll try Privoxy instead.] [Edit: uTorrent does not crash or corrupt the tracker name when using an HTTP proxy, but it claims to be updating when Privoxy logs no such connection attempt. However I can manually connect using PuTTY through Privoxy, though for some reason Privoxy did not receive the expected from the private tracker (tracker immediately closed the connection, possibly it didn't like the exact way I connected via PuTTY), but the connection attempt at least logged in Privoxy's log window (enable debug 2 in the config to see that stuff). So HTTP proxy doesn't seem to work right either in uTorrent for tracker updates on the torrent I posted. Other connections through the HTTP proxy to uTorrent's update server and app server and to peers are logged.]
  3. A screenshot + the torrent file itself would be nice. I don't see the devs fixing such an issue (if there is one) without those. I just figured out it's torrents from a particular private tracker. I've x'ed out my identifying ID number from one of the torrents and uploaded it here: http://getoffmyinternet.mzzt.net/test.torrent I reproduced the crash with it on build 26904 and submitted a dump using the crash handler UI. Sometimes it crashes sometimes it doesn't' date=' but you'll see the string corruption going on in the Trackers tab. I should also mention (yeah this is probably important) I'm running the Windows 8 Community Preview x64. I don't recall if I had problems on Windows 7 x64. I might try tomorrow to see if it's an OS-specific issue. I think that may be likely since I see nothing about this issue on the private tracker's forums, so it can't be a global issue with utorrent across all system configurations. Also the string corruption only occurs once the torrent is started. The strange error "Cannot get SSL chunk size" is shown sometimes in the tracker tab for the first update, probably because of the string corruption causing it to try and connect to a nonsense address or something along those lines.[/quote'] I have discovered another requirement for this bug to happen, you must have a socks4/5 proxy enabled, specific settings don't seem to matter. I used Tor. A fresh install of uTorrent 3.1 or 3.2 on a clean XP install can easily repro the issue. This is a serious issue as it prevents torrents like the one I posted from working AT ALL. Evidence of memory corruption too as you can see the tracker url getting corrupted in the tracker tab (though only in Windows 7, on XP you get an instant crash when viewing the tracker tab for the torrent).
  4. Still getting the string corruption and crashes with this new build (see my previous post).
  5. A screenshot + the torrent file itself would be nice. I don't see the devs fixing such an issue (if there is one) without those. I just figured out it's torrents from a particular private tracker. I've x'ed out my identifying ID number from one of the torrents and uploaded it here: http://getoffmyinternet.mzzt.net/test.torrent I reproduced the crash with it on build 26904 and submitted a dump using the crash handler UI. Sometimes it crashes sometimes it doesn't, but you'll see the string corruption going on in the Trackers tab. I should also mention (yeah this is probably important) I'm running the Windows 8 Community Preview x64. I don't recall if I had problems on Windows 7 x64. I might try tomorrow to see if it's an OS-specific issue. I think that may be likely since I see nothing about this issue on the private tracker's forums, so it can't be a global issue with utorrent across all system configurations. Also the string corruption only occurs once the torrent is started. The strange error "Cannot get SSL chunk size" is shown sometimes in the tracker tab for the first update, probably because of the string corruption causing it to try and connect to a nonsense address or something along those lines.
  6. Both 3.1.3 and the latest 3.2 beta have a serious issue... if you have any torrents running with tracker urls associated with them the tracker urls become corrupted (you can see it in the trackers tab) and pretty soon the whole thing crashes. I suspect it malformed the particular torrent files at some point, maybe, since new torrents I add don't seem to have any problems... anyways it may help if uTorrent is more tolerant of malformed torrent files or at least it should be able to detect them?
  7. Build 21882 doesn't work for me. It installs, but no window is shown. It keeps one core at 100% CPU... I hooked up Process Monitor to it and it is still making peer connections in the background, there's just no UI and it's maxing out a core. [Edit: Whew, it's not just me, ok.] Had to revert to build 21738, which works fine... is there some place I can more easily find old versions? Google wasn't too helpful since most sites that advertised the old build had already uploaded the new one and Google's cache was old. [Edit: Oh wow this is fun, left the uBrowse app running in the background and it ate up the ENTIRE 32-bit memory space until uTorrent started spouting out of memory errors. Yeah, apps shouldn't be able to do that.]