1.7 build 1875: Application Error (0x037f1069 referenced 0x00000023)

[zortonman]

I was deleting some torrents in a label list with 50-60 items when I received the following error:

uTorrent 1.7 BETA: uTorrent.exe - Application Error

The instruction at 0x037f1069 referenced memory at 0x00000023. The memory could not be read.

Click OK to terminate the program.

I had changed the sort order in the list a couple of times on different columns, and I had deleted 2-3 items from the list. FWIW: there were torrents downloading and seeding, but I think all of the ones in the list were seeding.

In terms of collecting information, I couldn't come up with much. I left the error dialogue up and poked around using Sysinternals process explorer. All but one of the threads seemed to be running periodically, with some threads running quite a bit. I copied the call stack for each thread, and I have included it below. I'm not sure whether this will be of any use, but what the heck.

The problem has not recurred, and build 1875 has now been running for 24 hours without another error. That said, I haven't done much in the way of torrent deletions.

BTW, congrats on a truly fine piece of software. These beta builds have been quite stable overall, and uTorrent in general is a marvel!

The stack traces are:

ntkrnlpa.exe+0x6dbeb

ntkrnlpa.exe+0xcb63f

ntkrnlpa.exe+0xcb78b

ntkrnlpa.exe+0x13ba29

ntkrnlpa.exe+0x13be87

ntkrnlpa.exe+0x6986c

ntdll.dll!KiFastSystemCallRet

!XcptFilter+0x161

!RegisterWaitForInputIdle+0x49

ntkrnlpa.exe+0x6dbeb

ntkrnlpa.exe+0x2b462

ntkrnlpa.exe+0x2bd44

ntkrnlpa.exe+0xe807c

ntkrnlpa.exe+0x6986c

ntdll.dll!KiFastSystemCallRet

!WaitForSingleObject+0x12

!GetModuleFileNameA+0x1b4

ntkrnlpa.exe+0x6dbeb *** this thread doesn't appear to be running ***

ntkrnlpa.exe+0x2b462

ntkrnlpa.exe+0x2bd44

ntkrnlpa.exe+0x9fcbb

ntkrnlpa.exe+0x6986c

ntdll.dll!KiFastSystemCallRet

!GetModuleFileNameA+0x1b4

ntkrnlpa.exe+0x6dbeb

ntkrnlpa.exe+0xe807c

ntkrnlpa.exe+0x6986c

ntdll.dll!KiFastSystemCallRet

ntdll.dll!RtlEnterCriticalSection+0x46

ntdll.dll!KiUserApcDispatcher+0x7

[Ultima]

Do you happen to be using NOD32?

[zortonman]

Nope, I'm using avast.

In case it's relevant, my machine is a Core 2 Duo E6600.

[Ultima]

Hm, can you get Process Explorer from sysinternals.com, run it, File > Save, then post the contents of the saved process list in the .txt file here?

Edit: http://forum.utorrent.com/viewtopic.php?pid=252004#p252004

Were you doing anything like this when it crashed? I just managed to get a memory read error via that method of crashing µTorrent.

[zortonman]

Before posting, I looked at the bug you mentioned. At the time, I thought the way in which uTorrent crashed was different, if you're getting an error that is similar to the one I reported, I'll give it a try.

[Firon]

1952 is out, in case you wanna try to see if it crashes.

[zortonman]

I have not encountered this problem in build 1952 nor 2145.

Thanks very much for your efforts!

[Ultima]

I guess the problem *was* related then... To be honest, I wasn't really sure your problem was related, as I only managed to get the memory read error once while messing with the bug. Good to hear that it's fine now

[zortonman]

I guess it's one of those nasty, indeterminate outcome problems where all one can say is: "it hasn't happened in a while, so I guess it's fixed". In my career delivering software products, this means either:

1) the problem actually is fixed , or

2) the problem won't re-appear until the day after you ship the final build, or your boss or most important customer installs it.

I'm optimistic that it is the former, because I've done a bunch of the same steps that originally caused it, and it hasn't happened again. Regardless, thanks very much for your efforts!