I have a few very large batch torrents in my queue, and it seems to cause ktorrent to use an insane amount of memory.

Heres a screenshot of "top":


The blocks at the top are OSDs from ktorrent that haven't been able to actually display yet, been there for ages now. ktorrent's main gui is also locked up, pending whatever its doing still.

svn info:

Code: Select all

moose@natasha:~/build/ktorrent$ svn info
Path: .
URL: svn://anonsvn.kde.org/home/kde/branches/extragear/kde3/network/ktorrent
Repository Root: svn://anonsvn.kde.org/home/kde
Repository UUID: 283d02a7-25f6-0310-bc7c-ecb5cbfe19da
Revision: 750461
Node Kind: directory
Schedule: normal
Last Changed Author: guisson
Last Changed Rev: 749973
Last Changed Date: 2007-12-18 04:51:05 -0700 (Tue, 18 Dec 2007)


side note, I'm running this on my "new" quad core desktop with 2GB ram, and its taking a while to start (swapping like mad), you should see how long it took on my older Atlhon 2800+ with about 400 useable memory (its an xen dom0). So far it stands at 1.3GB ram "RES", 1.7 "VIRT", and nearly 3GB of my swap is used (normally its never touched).

edit: I've got a full debug mode, so I'll try capturing stdout, since you might ask for it...

edit2: here is a log of all the output for a 3~ hour run of ktorrent. Some notes, it never actually got fully started, the main gui was frozen, only one of the OSD popups ever got properly drawn, and still it wouldn't accept input, or hide, and it seemed like it kept activating the same torrents over and over.. at least thats what it looks like in the log.

Which torrents are seeding and downloading, with the same torrents, I should be able to reproduce this.

I'm not sure what you mean?

The torrents that I moved out of the way to get ktorrent to actually start are #s 138, 142, and 143 (I dont actually have that many loaded, I used to a while ago, but some are still from then, they have taken a while to get as far as they have).

No I believe George is asking for a way to get the same torrents you have loaded, so he can download it to try to reproduce it on his end.

Either by a download link or emailing it to him.

Yeah, that was what I meant.

Sure, I can grab the cached torrent files if that'll work. Not sure how long it'll take to find the exact original ones again.


...


I've sent them off to your email, sorry if its a little large (over 1MB), compressing them didn't help much.

Another problem I've just had, it just froze up on me, and its causing one of my cores to run at 100%, and two of the last two lines in the log:

Unnecessary piece, total unnecessary data : 171.9 MB
Unnecessary piece, total unnecessary data : 172.0 MB

Not sure if they are connected, but they could be. I'm hoping the numbers are actual totals from the entire session, not the last couple chunks.. but this lockup is annoying. Since the ktorrent/* and downloads folder are over NFS (GbE network, throughput at about 300MB/s), it likes to lock up other access to NFS, so whatever its doing, its causing NFS to lock up as well, maybe its scanning data? But theres no scan dialog or any items in the log sating its rescanning data..