When looking in the peers section scrolling with the mouse wheel when scrolling back to the top and "overshooting" it will eventually cause a ktorrent crash.

Steps to reproduce: scroll down the list of peers with the mouse wheel and scroll back up, continue more than needed to get to the top of the list- it may not happen every time but it will in pretty short order.

I have scrolled like a mad man, and haven't reproduced it.

Got a backtrace ?

My guess is that it probably is a Qt bug.

George wrote:I have scrolled like a mad man, and haven't reproduced it.

Got a backtrace ?

My guess is that it probably is a Qt bug.

LOL The window reporting the crash and showing a backtrace doesn't show, it just crashes silently. Also I'm on gentoo I didn't use -g, not sure how useful gdb would be either.

Hmm- I was getting afraid of looking in the peers list and now that I want it to crash I cant get it too either. Dunno what to say, weird. It was crashing like crazy before...

EDIT: before when it crashed it did so in the peer list of a torrent that was downloading at a pretty high speed (a few MB/s), it's now seeding (at a few hundred KB/s) and now its not crashing anymore. Thats the only change I can think of.

As I suspected I was able to reproduce the crash again this time with a backtrace in the form of a .kcrash file too downloading a torrent at high speed- 7-8-9 thousand KB/s or so in this case. I got it to crash pretty quickly by scrolling up and down a number of times. Not sure how useful it is but here is the backtrace:

Application: KTorrent (ktorrent), signal SIGSEGV
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5dbd700 (LWP 15406)]
[New Thread 0xb3359b90 (LWP 15413)]
[New Thread 0xb45aab90 (LWP 15412)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe424 in __kernel_vsyscall ()
[Current thread is 0 (LWP 15406)]

Thread 3 (Thread 0xb45aab90 (LWP 15412)):
#0 0xffffe424 in __kernel_vsyscall ()
#1 0xb619c517 in poll () from /lib/libc.so.6
#2 0xb66e7bda in ?? () from /usr/lib/libbtcore.so.7
#3 0xb66e7c8f in ?? () from /usr/lib/libbtcore.so.7
#4 0xb66e8710 in ?? () from /usr/lib/libbtcore.so.7
#5 0xb7d710c2 in ?? () from /usr/lib/qt4/libQtCore.so.4
#6 0xb7d03160 in start_thread () from /lib/libpthread.so.0
#7 0xb61a5c0e in clone () from /lib/libc.so.6

Thread 2 (Thread 0xb3359b90 (LWP 15413)):
#0 0xffffe424 in __kernel_vsyscall ()
#1 0xb7d06be5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2 0xb7d7179c in ?? () from /usr/lib/qt4/libQtCore.so.4
#3 0xb7d713fa in QWaitCondition::wait () from /usr/lib/qt4/libQtCore.so.4
#4 0xb66e7666 in ?? () from /usr/lib/libbtcore.so.7
#5 0xb66e8710 in ?? () from /usr/lib/libbtcore.so.7
#6 0xb7d710c2 in ?? () from /usr/lib/qt4/libQtCore.so.4
#7 0xb7d03160 in start_thread () from /lib/libpthread.so.0
#8 0xb61a5c0e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb5dbd700 (LWP 15406)):
#0 0xffffe424 in __kernel_vsyscall ()
#1 0xb616fba6 in nanosleep () from /lib/libc.so.6
#2 0xb616f9bf in sleep () from /lib/libc.so.6
#3 0xb70fdf77 in ?? () from /usr/lib/libkdeui.so.5
#4 0x00000000 in ?? ()
#0 0xffffe424 in __kernel_vsyscall ()

Backtrace isn't very useful, the thread which crashes isn't shown.

Maybe you could install some debug packages, to get a better backtrace :

http://techbase.kde.org/Development/Tut ... sh_reports

Yeah, but I don't have debug packages on gentoo, I'd have to recompile all the relevant components (on a celeron D ). The interface gets very sluggish at that speed so that even the blue box around the peers tab when I go to switch to it takes some time to show. Perhaps it has something to do with high CPU usage at that speed (ktorrent does use most of the processor). Oh and now one time it crashed simply after going to that tab so I think scrolling in there just makes it more likely to crash.

I will see if I can test this with a local high speed torrent

Now it crashed when I tried right clicking on a torrent downloading at 7-8 thousand KB/s. Shouldn't be hard to reproduce by the looks of it.

EDIT: Update: it crashes like clockwork now during emerge --sync, not sure if it's the CPU usage or the disk activity or both, it seems to work without crashing while compiling something.

This should be fixed now (see http://ktorrent.org/forum/viewtopic.php?p=14566#14566)

Great news, thank you. I hope there's a 3.1.5 with the fix soon

If 3.2 is gonna take a while longer could you release a 3.1.5 please ? Some trackers prefer to allow specific versions of clients so I can't use 2.2dev.

Both 3.1.5 and 3.2 beta1 should be released next weekend.

Ok, tks.