Today, I had a hang shortly after completing a file, too.
Last output:
completing->PerformFileComplete(NULL); !!!
FE...mumble...87: Suspending uploads of file.
FE...mumble...87: Resuming uploads of file.
(There were none of the usual good/bad messages afterwards, so the
hang must have occurred less than half an hour after the completion.
Note that I rarely get more than one completion per day, and hangs
don't happen more often than perhaps 2-3 times a month.)
The file in question was only about 6 MB. aMule was clearly hung,
not redrawing its window. I didn't check the CPU load. In previous
hangs of that kind, *Mule was actually idle.
Beginning of the backtrace (rest in attachment):
Program received signal SIGINT, Interrupt.
0x420751ba in calloc () from /lib/i686/libc.so.6
(gdb) where
#0 0x420751ba in calloc () from /lib/i686/libc.so.6
#1 0x42074827 in calloc () from /lib/i686/libc.so.6
#2 0x42075400 in calloc () from /lib/i686/libc.so.6
#3 0x420741a0 in realloc () from /lib/i686/libc.so.6
#4 0x40471fb4 in wxString::AllocBeforeWrite(unsigned) () from /usr/lib/libwx_gtk-2.4.so
#5 0x40472160 in wxString::GetWriteBuf(unsigned) () from /usr/lib/libwx_gtk-2.4.so
#6 0x4047349c in wxString::PrintfV(char const*, char*) () from /usr/lib/libwx_gtk-2.4.so
#7 0x4047346a in wxString::Printf(char const*, ...) () from /usr/lib/libwx_gtk-2.4.so
#8 0x0807bd1f in CUpDownClient::ReGetClientSoft() (this=0x903bd30) at BaseClient.cpp:1373
...
Putting a breakpoint at ReGetClientSoft and continung the program
did not cause the breakpoint to get triggered. gdb didn't let me put
breakpoints at wx* functions (seems weird - is this normal with
C++ ?), and I didn't have much time, so I gave up there.
- Werner