Hello all.

After upgrading from 3.2 i;ve noticed that memory usage has increased a lot. After a week ktorrent may consume up to 2Gb ram.


This and entry from top after a couple of days running ktorrent

Code: Select all

PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
30616 non7top   20   0 1076m 306m  14m S   14 15.2 971:52.62 ktorrent

I can confirm that. KTorrent 3.2.x was using about 20mb of RAM or so, 3.3 (release version) has eaten 150mb for about six hours

Yes, 3.3 is eating memory fast.

Is anybody using the tracker grouping script ?

George wrote:Is anybody using the tracker grouping script ?

I'm not

George wrote:Is anybody using the tracker grouping script ?

Me neither. But I think I'll start if it will work good

I'm using the script. For now I've updated to 3.3 and will check how it behaves.

The script is triggering a memory leak in krosspython, which is reported but hasn't been fixed yet.

I fixed a whole bunch of memory leaks last week, but those weren't really serious (mostly forgetting to cleanup stuff at exit, should not impact runtime memory usage).

Gonna do some more valgrind runs with running torrents.

Btw, which plugins are loaded ? Is DHT enabled ?

DHT was enabled, no plugins were running (maybe just stats and whatever is enabled by default)

In rev: 1051036

All memory freed, but only at exit.

Attached massif(valgrind) file.

Memory leak is in DHT code. Disabling it solves the problem.

Visited dht nodes list keep growing.

Seems to be fixed in 3.3.1

MoDaX wrote:Seems to be fixed in 3.3.1

Yes, I added some simple limits on DHT tasks, so when the lists grows to big they will just stop.