Memory leak in 1.3
Re: Memory leak in 1.3
Just to be sure, your cache isn't set to some ridiculously high amount. I assume the default shouldn't be all that high at all.
-
- Member
- Posts: 22
- Joined: Mon Oct 25, 2010 6:11 pm
Re: Memory leak in 1.3
cache-size: 512 (16 KiB blocks)
cache lifetime: 60 (seconds)
cache lifetime: 60 (seconds)
-
- Member
- Posts: 22
- Joined: Mon Oct 25, 2010 6:11 pm
Re: Memory leak in 1.3
seems to be a different problem but i don't want to leave it unmentioned:
when i rightclick a torrent and choose "open folder" the folder opens up
but deluge goes up to 100% cpu-usage and remains there until i kill it?!
when i rightclick a torrent and choose "open folder" the folder opens up
but deluge goes up to 100% cpu-usage and remains there until i kill it?!
Re: Memory leak in 1.3
flasher360 wrote:seems to be a different problem but i don't want to leave it unmentioned:
when i rightclick a torrent and choose "open folder" the folder opens up
but deluge goes up to 100% cpu-usage and remains there until i kill it?!
That might be related, what is the folder name where you keep the downloads? And have you tried changing to a different folder?
Re: Memory leak in 1.3
we are attempting to troubleshoot the problem so the answer is obviously going to be yes.flasher360 wrote:if you still want me to launch it "non classic" then i will do. should i?
I already told you about this issue, and the bug ticket, in reply to your first posts on this thread!flasher360 wrote:seems to be a different problem but i don't want to leave it unmentioned:
when i rightclick a torrent and choose "open folder" the folder opens up
but deluge goes up to 100% cpu-usage and remains there until i kill it?!
-
- Member
- Posts: 22
- Joined: Mon Oct 25, 2010 6:11 pm
Re: Memory leak in 1.3
launched it non-classic.
after some hours running:
deluged still consumes about 2,2% memory
/usr/bin/deluge goes up from 1,7% to somewhere ridiculous.
(the longer it's running the more memory it consumes)
so it seems that the deluge gtk/ui is causing the problems.
what to do next?
i found the ticket for the cpu-usage problem
and i wrote my informations there.
after some hours running:
deluged still consumes about 2,2% memory
/usr/bin/deluge goes up from 1,7% to somewhere ridiculous.
(the longer it's running the more memory it consumes)
so it seems that the deluge gtk/ui is causing the problems.
what to do next?
i found the ticket for the cpu-usage problem
and i wrote my informations there.
Re: Memory leak in 1.3
Ok thanks for testing.flasher360 wrote: so it seems that the deluge gtk/ui is causing the problems.
what to do next?
Please create a bug ticket with the relevant info from this thread. You should also add this forum thread link in the ticket and then post the ticket number here.
-
- Member
- Posts: 22
- Joined: Mon Oct 25, 2010 6:11 pm
Re: Memory leak in 1.3
new ticket for memory leak: http://dev.deluge-torrent.org/ticket/1454
older ticket for "open folder" cpu problem: http://dev.deluge-torrent.org/ticket/1396
older ticket for "open folder" cpu problem: http://dev.deluge-torrent.org/ticket/1396
Re: Memory leak in 1.3
I am seeing the memory and CPU issue as well on Debian 5.
-
- Member
- Posts: 22
- Joined: Mon Oct 25, 2010 6:11 pm
Re: Memory leak in 1.3
then please post your system-settings and deluge/libtorrent versions in the ticket mentioned above.teh_g wrote:I am seeing the memory and CPU issue as well on Debian 5.
thanks.