I just upgraded to the latest SVN earlier today - I think it's 1145436 for both ktorrent and libktorrent - and now even without uTP, ktorrent is using huge amounts of memory - my 8GB box is 3GB into swap, when normally it uses no swap. According to htop, ktorrent is using 8780M virtual, and 6073M resident. I hit Ctrl-Q, and ktorrent doesn't seem to want to go away, either. I have to pkill it. Once I do that, RAM usage drops to 1.3GB and swap of 915MB (these numbers don't indicate issues with ktorrent, just a baseline for comparison).

Don't see any huge memory usage a startup with latest SVN.

What plugins have you got enabled ?

It's not at startup that memory shoots through the roof. Generally, I've only noticed it after starting it, going away for some time (e.g., hours), and coming back to a sluggish system.

Then again, I just started it now, and it's got high CPU usage, and memory is going up fast.

I have Bandwidth Scheduler, Download Order, Information Widget, Log Viewer, Scripting, Search, and UPnP plugins enabled.

I barely had time to write this before the system started swapping. It was already so bad, I had to kill it. Note that I also have four torrents going, plus at least a few torrents seeding, and a bunch queued for seeding.

Found the problem, it was vector always growing in size due to a recent change

Thanks - though now I can't compile libktorrent. At svn 1146338, I get:

Code: Select all

/var/tmp/portage/net-libs/libktorrent-9999/work/libktorrent-9999/src/tracker/udptrackersocket.cpp: In constructor ‘bt::UDPTrackerSocket::UDPTrackerSocket()’:
/var/tmp/portage/net-libs/libktorrent-9999/work/libktorrent-9999/src/tracker/udptrackersocket.cpp:97: error: cannot allocate an object of abstract type ‘bt::UDPTrackerSocket::Private’
/var/tmp/portage/net-libs/libktorrent-9999/work/libktorrent-9999/src/tracker/udptrackersocket.cpp:45: note:   because the following virtual functions are pure within ‘bt::UDPTrackerSocket::Private’:
/var/tmp/portage/net-libs/libktorrent-9999/work/libktorrent-9999/src/net/serversocket.h:82: note:        virtual void net::ServerSocket::DataHandler::readyToWrite(net::ServerSocket*)


I'm not sure if I'm missing something?

This little patch seems to work ... though I somehow suspect it's the wrong solution as I'm not getting peers as quickly as usual. I think. Hard to tell.

That compile error has also been fixed