[Windows GTK client] Major issue with memory consumtion
Posted: Fri Nov 18, 2011 7:21 pm
Hi,
I'm experiencing some troubles with the memory consumption on Deluge GTK client (v1.3.1) on Windows XP SP3. When most of the time it only uses 40-60MB of RAM, sometimes (I don't know when) it reaches 600MB or even more and then keep growing until I have to close and restart it.
What is particularly odd is that I use the GUI only as a client to connect to a daemon (same version of course) running on my home server (Debian Squeeze), so basically the client does not handle files download at all in my configuration. The daemon itself is nicely stable and uses around 300MB maximum at all time (but I don't really care as long as it's lower than 800MB, the server has enough RAM).
I've attached a screenshot showing the situation after approximately 24h running (I added some *big* torrents to the queue in the meantime, two of them were 50GB+ large, don't know how it could be important though).
I guess there's a memory leak somewhere that could explain this behaviour. I've searched the forum but those who were reporting a similar problem were using the "Classic" mode of Deluge, so in some cases I can understand that downloading large files may explain the memory consumption. But in my case I don't see the point.
I'm using the 3 following plugins:
- Blocklist
- Label
- Stats
I've just disabled Stats to see if it makes a difference in the next days.
If I forgot some crucial information, please tell me. I may create a ticket soon if nobody can tell me how to fix this by tweaking the configuration (even if I'm pretty sure it's a bug, not a feature ^^).
Thanks in advance
PS: typical remark but anyway, sorry for my English
PS 2 : 10mn after the screenshot, Deluge is now at 930MB and keeps growing...
I'm experiencing some troubles with the memory consumption on Deluge GTK client (v1.3.1) on Windows XP SP3. When most of the time it only uses 40-60MB of RAM, sometimes (I don't know when) it reaches 600MB or even more and then keep growing until I have to close and restart it.
What is particularly odd is that I use the GUI only as a client to connect to a daemon (same version of course) running on my home server (Debian Squeeze), so basically the client does not handle files download at all in my configuration. The daemon itself is nicely stable and uses around 300MB maximum at all time (but I don't really care as long as it's lower than 800MB, the server has enough RAM).
I've attached a screenshot showing the situation after approximately 24h running (I added some *big* torrents to the queue in the meantime, two of them were 50GB+ large, don't know how it could be important though).
I guess there's a memory leak somewhere that could explain this behaviour. I've searched the forum but those who were reporting a similar problem were using the "Classic" mode of Deluge, so in some cases I can understand that downloading large files may explain the memory consumption. But in my case I don't see the point.
I'm using the 3 following plugins:
- Blocklist
- Label
- Stats
I've just disabled Stats to see if it makes a difference in the next days.
If I forgot some crucial information, please tell me. I may create a ticket soon if nobody can tell me how to fix this by tweaking the configuration (even if I'm pretty sure it's a bug, not a feature ^^).
Thanks in advance
PS: typical remark but anyway, sorry for my English

PS 2 : 10mn after the screenshot, Deluge is now at 930MB and keeps growing...