I have ktorrent running on a separate computer that is run headless most of the time, with the exception of major problems that cannot be fixed by SSH. Recently I have been having problems with ktorrent becoming unresponsive via the webgui interface. When this happens the webgui will simply not load and come up with a timeout error, I then login via SSH and run "top" usually two separate PIDs of ktorrent are running when this happens. To get it working again I run "kill PID#" and then "ktorrent --display :0" and everything is up and going again.

What I am really asking for, is where do I need to look to find the crash log files to post up to help better diagnose the problem and what else can I do to help narrow down what is happening.

I am running ktorrent v2.1.3 compiled from source and slackware 11.0

Thank you

Do you have DHT enabled ? If it is the DHT crash bug, then it should not happen with DHT is disabled.

George wrote:Do you have DHT enabled ? If it is the DHT crash bug, then it should not happen with DHT is disabled.

I'm not sure, but I believe that it is enabled. I'll check when I am at that computer next.


Oh, well I was typing this I got an error on my SSH terminal after restarting ktorrent.

"Qt: Warning: QGArray::at: Absolute index 0 out of range"
"KCrash: Application 'ktorrent' crashing..."

P.S. I am currently updating to 2.1.4 and will see if this fixes the problem

Well, running 2.1.4 has been stable for about 1-2hrs now. I will update in a day or when in crashes next, whatever happens first.

EDIT: Well it is still up as of about 4-5hrs so I am hoping that it was the DHT problem. Thanks to everyone who works on ktorrent for the quality program.

EDIT2: It has been about 12hrs with no problems. I am assuming that it was the DHT bug that was causing the problems. Thank you for the help.

We think it is another client sending malformed DHT packets which we didn't handle properly.

It seems this client only saw widespread use pretty recently, because this bug didn't show up a month ago, and now we have people bombarding the forums and bugs.kde.org.