SABnzbd Forums

High memory usage in 0.5.0 beta1 (did not occur in 0.4.12)

I am running Windows 7 (64bit), with 2gig ram.
This system is dedicated to SABnzbd downloads and playing of downloaded content
using Media Player Classic.  The syste, has a bare install other then a few programs like:
Winamp
SABnzbd
Media Player CLassic
AVG (ANti-Virus)

Also to note: I am using the Plush interface.

At startup, SABnzbd.exe *32 shows 50% CPU and memory climing (over 1.5 minutes) to 609,104k.
System response is normal.

After running for 2 hrs, SABnzbd.exe *32 still shows 1% (to 2%) CPU and memory has only
climbed to 610,344k.  System response is still normal.

After running for 5 hrs, SABnzbd.exe *32 still shows 1% (to 2%) CPU and memory has only
climbed to 622,288k.  System response is still normal.

After running for 48 hrs, SABnzbd.exe *32 shows 1% (to 2%) CPU and memory reacheed 808,468k (without decrease)
The system also becomes sluggish.  

Performing a SABnzbd restart returns the system to initial memory and normal perfomance.
This did not occur in 0.4.12 version.

Any ideas, suggestions, comments ?



Regards,
TechDude

Does all of this happen when SABnzbd is just idle
or does it do any work in these hours?

Hi shypike,

SABnzbd is working full time... 24/7.
Download rate is set to 300 KB/s.

Downloads are mainly single episode shows, plus full seasons.

After running for 24 hrs, SABnzbd.exe *32 still shows 1% (to 2%) CPU and memory has only
climbed to 615,012k.  System response is still normal.

So far, past 24 hours has been good.


Regards,
TechDude

The high memory issue occurred twice... however, this time it does not appear to be occurring.

After running for 48 hrs, SABnzbd.exe *32 still shows 1% (to 2%) CPU and memory has only
climbed to 640,772k.  System response is still normal.

Although memory is climbing (very) slowly... it is by far at the pace it was prior.

I will continue to monitor and let you know.

It could be the Python garbage collector.
I can imagine that it drags behind when SABnzbd is very busy.
It's problem with all "dynamic" languages (Python, Perl, Ruby etc.):
as a programmer you don't need to worry about cleaning up storage
but you also never know when  the garbage man person comes along.

If memory usage is only even rising and never going down, that's
a strong indication of a memory leak.

The memory climb issue did not occur in 0.4.12 version
... it is also not occurring in RC3

In fact, RC3 has great use of memory now, with average of only 40,000 k
vs 600,000k in the beta versions.

Awesome work everyone!

Good to hear.
Thanks for your feedback.