Hi, this is my first time posting, I hope someone can give me a hand.

So, I came back to my Ubuntu 6.10 install the other day, on an Althlon64 3200+ with 512mb ram, and found that it was hung. I manually restarted it, and tried to load all the programs I had up when the system had gone down, but I found that whenever I tried to start ktorrent, it would start eating up all my resources (top says up to 130%+ memory usage) - it's never done this before, even when loading lots of large torrents.

Version info:
rhadamanthos@Heavyarms:~$ ktorrent --version
Qt: 3.3.6
KDE: 3.5.5
KTorrent: 2.0.3


I started it with the --debug option, and got the following (snipped for brevity):
rhadamanthos@Heavyarms:~$ ktorrent --debug
X Error: BadDevice, invalid or uninitialized input device 166
Major opcode: 144
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 166
Major opcode: 144
Minor opcode: 3
Resource id: 0x0
Failed to open device
(snip)
Loading 14 active chunk downloads
Loading chunk 56
Loading chunk 536871048
Illegal chunk 536871048
(snip)
Loading 21 active chunk downloads
Loading chunk 633
Loading chunk 128
(hang)

The system just grinds to a halt on chunk 128 of that particular torrent, and starts eating up all my resources. I assume the "illegal chunk" messages are from chunks that are inconsistent because they were being downloaded when the system crashed the first time. However, I'm in a bit of a bind. I can't seem to find which file this chunk 128 belongs to, and I can't find a way to clear my download chunk cache, so I can't start the torrent client.

Is this a bug? What other information would I need to file along with it? If it's not a bug, or I'm doing something wrong, how can I recover my torrents/be able to use my client again?

Thanks.

It seems some files got corrupted.

To get things running again, you should go to ~/.kde/share/apps/ktorrent

There will be a couple of directories named tor1, tor2, ...

In each of these directories is a file named current_chunks, just delete them all. You will lose some data, but not that much.

Thanks, that totally worked. All my torrents are back!

I'm glad it wasn't a bug.

Well it is a bug, this shouldn't happen, even if the data is corrupt. I have made some fixes which should prevent this. They will be part of our next release (2.1.1)