Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[woutermense]

aMuleGUI crashed after the following:

- choose other category
- change the sort order of the progress bars
- click one of the downloads

Before this there were already some glitches in the progress bars - some didn't show. These glitches seem to appear after idling a while.

attached is a .dmp file for Visual Studio

[Stu Redman]

I'm afraid dmp files are useless for this pupose. AFAIK it only works if you build an exe, keep the exact build environment, then give someone the exe. If he returns the dmp to you, you can debug it. I can't, although I've tried to build the app from the same tarball.
Just run it out of the studio, and if it crashes, tell us about the place in the app where it does.

Also, there is a rewrite of the EC going on at the moment, and I don't know if it is currently stable (or even supposed to work at all). Try the MSVC solution from 20080912 and the rest from 20080910.

[woutermense]

Ahw that's too bad, so these dmp files are only useful for distributed executables right? Isn't there another way to generate a backtrace or something? Just telling at which place in the source it crashes seems a bit unreliable to me.

[Stu Redman]

Why ? Usually, the important part of a stack trace are just the last 2-3 frames of the app. Select them so that the code shows, make sure the variables window is there, then make a screenshot for each of these frames. Much better than a backtrace. 
Anyway, we can call that EC bug now confirmed, with 4-5 independent error messages.

[woutermense]

So, I should post it like this? Or do you need more information?

Btw. this crash was generated under the same circumstances, but with SVN20080916

[Stu Redman]

Yeah, that's almost fine. But you should point the call stack to the last call from aMule itself not wxWidgets.
Problem is, the crash is deep inside the libraries and gives no real clue (like most of the linux backtraces, alas).

Before this there were already some glitches in the progress bars - some didn't show. These glitches seem to appear after idling a while.

So you get the crash only after a while, and after graphics starts getting crappy ? Well, there is a known problem with high GDI resource usage on Windows which leads to all kind of misbehaviour. A fix is prepared and being carefully reviewed at the moment. I'll commit it as soon as I get the go and tell you.

[woutermense]

Hey I keep getting similar errors, and with 100+ downloads in the queue this is happening more and more often. So, any news on this, since it seemed to me that there was already a fix and that it was just being reviewed before comitting?

[Stu Redman]

"Just" can also stand for "just a little longer than expected". 
You can get the patch here, and it's also discussed here.