yvan2k Posted May 26, 2011 Report Share Posted May 26, 2011 Hello.uTorrent version: 3 (build 25327) and lowerOS: Windows XP SP3 32-bitProblem: Crash on start if upon start uTorrent can't find one of the torrent files registered in resume.dat.Expected behaviour (as in 2.x line): uTorrent loads fine, in status column for missing torrent shows message "Can't open .torrent file: %s".Curiously, if you don't close crash dialog uTorrent seems working just fine, but torrent loading stops on first missing torrent. I guess it means that crash happen in thread that load torrents. Bug don't exist in v2.x line, but happens every time with v3.0 regardless of directory for storing torrents. Link to comment Share on other sites More sharing options...
moogly Posted May 26, 2011 Report Share Posted May 26, 2011 If you have some crashdumps (.dmp) in the folder %appdata%\utorrent, upload them to http://www.mediafire.com/ then send the link to Firon by email. Link to comment Share on other sites More sharing options...
yvan2k Posted May 27, 2011 Author Report Share Posted May 27, 2011 Just decided to see what's inside dump file and OMG - too much personal information about my system. Anyway, i strongly believe dump is not necessary - issue clearly reproducible. Don't get my wrong, i know how to code/debug, and this is not some sort of layman excuse. And i myself had 5 year pleasure supporting software with all sorts of angry and stupid users. Again - this is finely reproducible bug. Thanks anyway. Link to comment Share on other sites More sharing options...
moogly Posted May 27, 2011 Report Share Posted May 27, 2011 How do you think the devs can fix the issue if they don't have the crashdumps? Sometimes the crash is due to a tierce software injected into µT, not µT itself. Of course, the dump reports info on the system. Link to comment Share on other sites More sharing options...
Firon Posted May 27, 2011 Report Share Posted May 27, 2011 Please give us the dump. Link to comment Share on other sites More sharing options...
yvan2k Posted June 13, 2011 Author Report Share Posted June 13, 2011 Bug is gone with Version 3.0 RC4 (build 25345). Thank you for fixing. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.