Registered Member
|
Thanks largely to George for helping me understand kross, ive managed to put together a basic script to auto sort torrents. unfortunately it has a huge memory leak, so do not use it:
~/.kde/share/config/ktorrentsorter/string is
the memory starts haemorrhaging when you actually click on a group, to me this suggests that the problem is in the isMember function, unfortunately i don't see what I'm doing wrong, is there a problem with the Kross interface? I know i can work around this (redo subgroups to do the work on addition), but it doesn't seam like a nice way of doing it and I'm away from a sober state for the rest of the week p.s is there a good community for python noobs to get feedback on scripts (e.g what im doing wrong) as most of my mistakes are probably not KTorrent/Kross specific? |
Moderator
|
I see the memory leak to, a 100 KB every couple of seconds.
Looking at the code I don't see anything wrong, in isMember nothing is added to a list or a dictionary or something else. So I started the tracker grouping script, and that showed the same behavior. It must be in KT itself or in Kross. But I don't see anything obvious in the scripting plugin which could leak memory. Update: it is definitely where KT calls the script's isMember call (through kross) which is leaking memory. It's got to be in kross. |
Moderator
|
|
Registered Member
|
thanks, I'm still working on the script, unfortunately as i don't know c (yet) i'll have to just keep an eye on the report for now
|
Registered users: Bing [Bot], Evergrowing, Google [Bot]