Actually in 3.3.4 I still get this massive memory leak if I enable scripting and the "group by tracker" script.

At least sucking up over 3 GiB of RAM is something I'd consider a leak. If I kill KTorrent (won't die otherwise) and then turn off scripting it works normally.

hook wrote:Actually in 3.3.4 I still get this massive memory leak if I enable scripting and the "group by tracker" script.

At least sucking up over 3 GiB of RAM is something I'd consider a leak. If I kill KTorrent (won't die otherwise) and then turn off scripting it works normally.

You will have to upgrade to 4.0.5, to get rid of this permanently. The real problem is in krosspython but 4.0.5 has a workaround so that the leak is not triggered.

George wrote:You will have to upgrade to 4.0.5

Is 4.0.5 released?

It is now

George wrote:You will have to upgrade to 4.0.5, to get rid of this permanently.

Thanks, emerging it as I type this

The real problem is in krosspython but 4.0.5 has a workaround so that the leak is not triggered.

Is there anything being done with KrossPython on that matter then?

The bug has been reported along with 2 others, but none have been fixed yet.

George wrote:The bug has been reported along with 2 others, but none have been fixed yet.

I found one and voted already. Could you post the other one, so I can do the same?

https://bugs.kde.org/show_bug.cgi?id=203922
https://bugs.kde.org/show_bug.cgi?id=231138
https://bugs.kde.org/show_bug.cgi?id=238668