Hi!

I found out that also the new 2.1 version freezes on my system.
As far as I can see at the moment it freezes only when downloading a torrent AND simultaniously updating the IP-Filter. As soon as it starts to download the filter, ktorrent freezes and it takes the whole system with it.

Is there anything known about that or anything I can do about it other than waiting for every download to finish and update the filter after that when not downloading anything else?

Thanks!

Weird... I'll check it out.

It works here.

Tell me, freeze happens while you download IP filter, not while converting, right? We use KDE classes to download IP filter, KT does not have much to do with it.

What's your KDE version?

I think I just had bad timing. I just found out that it also freezes when just running a download. It freezes faster when converting the downloaded filter file, but also does during simple download. I have KDE 3.5.6 running. Maybe I can get some backtrace, but this is getting difficult since the whole system starts following Ktorrent once it starts freezing. I'll see what I can do.... meanwhile, what do you think could cause the crash? I mean, I just download and do nothing else and after a short while this weird behavior starts. And this happens since version 2.0 when I first started using ktorrent...
I wasn't able to debug it since the rest of the system usually freezes very fast once ktorrent starts freezing.

Thanks for the help!

I have no idea. I'll upgrade to KDE 3.5.6 later this week (if my ISP finally chooses to upgrade my connection) and I'll check it out with new KDE. Maybe it has something to do with that...

I also have no Idea about what's wrong. I had tis problem also with previous versions of ktorrent and kde. I tried to get some output from gdb, but as soon as ktorrent starts freezing, I can't even press ctrl+c even if focus is already on the console. So I decided to keep watching and write down manually what output may appear. To my surprise there was noting. By nothing I mean that different threads were started during download and stayed there during ktorrent works. But after that when the program freezes there's no extra output showing up. Nothing. I kept watching till everything froze but there was no message showing up at the console....
This happened several times also after completely deleting every file related to ktorrent. I removed every config I could find and the same thing happened again and again.....

Is there any other way, maybe to store the output live while everything runs till freezing starts? Some way to record live into a text file which I can still open after pushing the reset button? Maybe this could work?

Thanks!

Is there any useful info at the end of KT log file, maybe we can get a hint what's going on, if it's KTs fault?

I posted the logfile here: http://pastebin.archlinux.org/1276

Maybe you can get something useful out of it

Nothing unusual there...

Anything else that might show what's wrong?

Well, a backtrace from breakpoint during freeze would be great but I don't know if you can do this.

It depends on how detailed your instructions are. I've never done a backtrace, because I never needed to. Besides that there's also the problem, that the whole system freezes, so I either have to save the output directly into a file or I have to write down the output manually while watching the console...
Just tell me what to do?

Running from gdb is not that difficult :

gdb /usr/bin/ktorrent

In gdb :
run --nofork

When it freezes hit CTRL + C, hopefully gdb will get some CPU time to stop it. Then you do :

bt

This will print out a backtrace. If running stops before the freeze, because of some signal, you can do cont to continue execution.

I don't know if the crash right now is like the ones before, because the system didn't freeze this time. But one thing is in common. Even after pressing ctrl+c in gdb ktorrent doesn't shut down. It simply keeps running. Anyway, I did bt and this is the output:

Code: Select all

(gdb) bt
#0  0x00002b35badf73f2 in ?? () from /lib/libc.so.6
#1  0x00002b35b969d770 in QEventLoop::processEvents () from /opt/qt/lib/libqt-mt.so.3
#2  0x00002b35b96fa481 in QEventLoop::enterLoop () from /opt/qt/lib/libqt-mt.so.3
#3  0x00002b35b96fa352 in QEventLoop::exec () from /opt/qt/lib/libqt-mt.so.3
#4  0x00000000004234d5 in ?? ()
#5  0x00002b35bad5f2f4 in __libc_start_main () from /lib/libc.so.6
#6  0x0000000000423139 in ?? ()
#7  0x00007ffff377ebd8 in ?? ()
#8  0x0000000000000000 in ?? ()


Again, I don't know if this crash is the same like before since the system didn't start acting weird.

Let me know if this helps!

Thanks!

Unfortunately, it doesn't help much. It gets stuck in Qt event loop, there's no info that could help us find the problem

Although, you should recompile KTorrent with debugging symbols enabled.