Jump to content

1.8.1 Release Candidate 1 (build 12549)


Firon

Recommended Posts

  • Replies 547
  • Created
  • Last Reply

Top Posters In This Topic

The release of uTorrent 1.8 was a sad day for me since it started crashing and hasn't ceased to do so up until now.

I read all the possible fixes and workarounds, I scanned my computer for viruses and malware.

Yes, I used Nod32 but i added uTorrent to the list of exceptions and it keeps crashing even when I turn off Nod32 anyway... :-\

The funny thing is that it never crashes while downloading, only when I'm seeding...

Perhaps this memory dump of the uncompressed version will help?

12183-utorrent_2d99.dmp (97 KB)

You have "the Vista bug". It happens to quite a few people, but there is no indication that it's a bug in uTorrent, from the crash dump. So, to narrow it down we'll have to find out what changed in 1.8 that causes it to happen more frequently.

How quickly does it happen? Is there anything you can do to make it happen more quickly? Would you be willing to run some test builds?

Link to comment
Share on other sites

I see a huge CPU, IO and Memory spike when opening the "relocate" dialog.

From 50MB to 112MB the first time then from 90MB to 120MB subsequent times (and rising). Plus it's really laggy.

edit: It just crashed when I continued on to relocating the ~14th file: http://www.mediafire.com/?3iyojywnixw

I see WMVCORE.dll and a bunch of Tortoise SVN dlls loaded when this crash occured. Maybe one of those?

Link to comment
Share on other sites

I uninstalled TSVN and turned off thumbnail gen.

I can reproduce it. All you have to do is open a lot of relocate dialogs then it crashes and can't save the dump when u click save on the last one.

dump: http://www.mediafire.com/?jlrlixc6x0s

I tried ticking the "application verifier" in "Global Flags" and that seemed to stop it from crashing.

Actually, I opened the dialog once this time: http://www.mediafire.com/?lqekwauibpm

I think it only happens if I wait until after the icons for the items in the favourites bar and then press save: http://www.mediafire.com/?6tiyetrt4ig

Hmmm... I don't know.. Nothing that similar about when it happens. Maybe when I quickly close one then open another: http://www.mediafire.com/?egwgky4vmop

Link to comment
Share on other sites

How quickly does it happen? Is there anything you can do to make it happen more quickly?

I'm quite bamboozled by this bug - there seems to be absolutely no pattern to it. Sometimes uTorrent runs fine for hours at a time and at other times it crashes just after logon.

Like I wrote before the crash seems to appear only during seeding - never got a crash while downloading (hence I'm still using uTorrent even though my ratio might suffer from it :-P).

When seeding uTorrent crashes from time to time as described above but it usually crashes VERY quickly when it is completely inactive, that is, has finished seeding/downloading/whatnot.

Would you be willing to run some test builds?

Of course - anything to help (me). ^^

uTorrent is by far my favorite client and I went through quite a few (been e.g. using Azureus for years).

uTorrent 1.7 was working fine for me on both Vista and *dun dun dun* Win2K (I skipped WinXP because I had bad experiences with it initially).

P.S. Here's a another dump - unlike the recent one this happened very quickly.

12183-utorrent_7ea7.dmp (104 KB)

P.P.S. I don't hate Vista although I'm dual-booting with Linux. In fact, there's no going back for me after I got used to its peculiarities. ^^

Link to comment
Share on other sites

unregister shmedia.dll and see your problem still happens.

Hmmm...

The module "shmedia.dll" failed to load.

Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent .DLL files.

The specified module could not be found.

.

shmedia.dll or anything named similarly doesn't seem to be anywhere on my system.

Link to comment
Share on other sites

Well, the latest update has stayed connected with all torrents for over a day so I would say that problem is solved. I set max_halfopen back to 8 and I'm still seeing x/8 connecting most of the time. Rarely drops off the 8 value. Bumped it to 25 just to see (I have tcpip.sys patched to 50) and within a minute it was at x/25 connecting and has stayed there for over an hour now. Not sure if that's a concern or not.

So thanks for fixing this one.

Now, can we look at why under 1.7.7 I can connect to 2x to 3x more peers than under 1.8 and 1.8.1? 8)

Again, thanks for all your efforts.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...