Memory Leak

[moffa]

Hi,

I just checked out the subversion last night and today when I returned to my computer it had taken over 1gb of memory. I took a screenshot but I don't know how to upload it.

I was running the blocklist and scheduler plugins.

Using Ubuntu 7.10 (Gutsy) AMD64

[anboni]

I experienced similar high memory usage yesterday, running revision 2195. I don't have any plugins enabled, running on Ubuntu 7.10 (32-bit). I'll update to 2204 and update this post with results.

*Update*

I updated to 2204, the memory leak still seems to be there. I did some more testing, deluge running with 2 torrents active (one 350MiB seeding, one 3.3GiB downloading), memory usage increased by somewhere between 0 and 500KiB per 2 seconds (monitored with 'watch cat /proc/<pid>/status'). When I pause both torrents, the increase seemed rarely to go above 200KiB, but there still was an increase. After about 20 minutes of running, the status file showed:

Code: Select all

Name:   deluge
State:  S (sleeping)
SleepAVG:       97%
Tgid:   18509
Pid:    18509
PPid:   1
TracerPid:      0
Uid:    1000    1000    1000    1000
Gid:    1000    1000    1000    1000
FDSize: 256
Groups: 4 20 24 25 29 30 33 44 46 108 109 110 1000
VmPeak:   410736 kB
VmSize:   374136 kB
VmLck:         0 kB
VmHWM:    284680 kB
VmRSS:    284680 kB
VmData:   332060 kB
VmStk:       152 kB
VmExe:       988 kB
VmLib:     27012 kB
VmPTE:       652 kB
Threads:        5
SigQ:   0/8191
SigPnd: 0000000000000000
ShdPnd: 0000000000000000
SigBlk: 0000000000000000
SigIgn: 0000000021001000
SigCgt: 0000000180004003
CapInh: 0000000000000000
CapPrm: 0000000000000000
CapEff: 0000000000000000
Cpus_allowed:   01
Mems_allowed:   1

When I wanted to close the application (via File/Quit), it froze (this might be the known issue.)

Interestingly, when I clear the configuration (renamed ~/.config/deluge), it appears the memory usage is stable as a rock. Then I added only the 350MiB torrent (well-seeded, so no activity), memory usage didn't move at all. Then I added another 350MiB torrent, downloading at 1.4MiB/sec, memory usage increased slightly (VmSize went from 86MiB to 94MiB over the coarse of downloading that file.) Now both are seeding and memory usage doesnt move. Then I added the 3.3GiB torrent back, deluge closed on me (it just disappeared, I hadn't thought of starting it from a terminal until then, so no traceback either :/ ). When I restarted deluge, it picked up all three torrents correctly and memory usage started increasing again.

Hope this info helps narrowing down the problem. If there's any other information that would help, I'd be happy to provide whatever i can.

[johnnyg]

I took a screenshot but I don't know how to upload it.

Under "Save", "Preview", "Submit", there should be an "Options" tab and next to that an "Upload attachment".

Specify the filename (comment is optional), add the file.

That should work, otherwise you can host it yourself and link to it using [img]url[/img]

[silverdulcet]

I've been experiencing the same thing.
Xubuntu Feisty on a Celeron 800mhz/512mb ram

I run deluge from the console, but there is no traceback that I have found. It almost locks the system up. I've got it to toss some errors by hitting Ctrl-C in the console window which sometimes allows me to close deluge, but it hangs at:
core: removing settings...

This doesn't always work. Most of the time I have to kill it by opening the process manager and killing the python process.

Any advice on what I might try to find useful error information is welcome.

[markybob]

this is only on svn, right? i'm looking into it. i'd appreciate some help on this if any of you guys are good programmers :p

[silverdulcet]

Yes, its only svn. I currently have 2204. I began running into the problem 2-3 revisions ago. Sorry I can't do more, but I am not a programmer.

[markybob]

this should be fixed in rev 2205. let me know if it isnt. unfortunately, i had to remove the advanced progress bar. if there are any programmers out there who would be interested in keeping the advanced progress bar, please take a look at 2204 and try to help us figure out the problem. thanks

[apoptosa]

this should be fixed in rev 2205. let me know if it isnt. unfortunately, i had to remove the advanced progress bar. if there are any programmers out there who would be interested in keeping the advanced progress bar, please take a look at 2204 and try to help us figure out the problem. thanks

Yay, you have indeed found the leak

[anboni]

Looks like 2205 fixes it, thanks loads It's been running for about 45 minutes now and memory sits tightly just over 90MiB.

Unfortunately, I'm not a very experienced programmer, I took a brief look at the diffs between 2204 and 2205, but can't make heads or tails from it. If anyone does make a change to enable the advanced progress bar and fix the leak, I'll be happy to give that version a whirl.

[moffa]

Hi, thanks for fixing it. I haven't programmed in years, so I'm not sure I'd be too much help.