Page 2 of 2

Re: Windows 7 memory leak

Posted: January 15th, 2010, 6:46 pm
by Skibumtx
Hmm,

tried totally disabling "Web Protection" but still leaking memory.

I can't really verify that it's related to ESET at this point, guess i need to try a different anti-virus to really tell.

Ski

Re: Windows 7 memory leak

Posted: January 21st, 2010, 2:39 pm
by Skibumtx
I went so far as to remove EST and switched to Comodo - still having the issue but it doesn't seem as prevalent.

Ski

Re: Windows 7 memory leak

Posted: May 24th, 2010, 6:38 pm
by MPenguin
Registered here because I'm experiencing the same issue.

I'm fairly new to Sabnzbd, but I already enjoy it much more than Newsleecher. The only problem with it is the horrible memory leak on Win 7 x64. I'm on an older system (X2 4400, 4 gb DDR Ram), but the only I seem to notice it is when I run Sabnzbd.

Generally, if I let it run overnight, I'll wake up in the morning to find it has either frozen or my system is using ~3.75gb of my 4gb of memory. This was happening with NOD32 4.0.xxx x64. Today I tried updating to the latest 4.2.xxx and we'll see how that goes.  I've also tried disabling web access protection.

If it's still a nogo, I'll try Microsoft Security Essentials. I have tried it before, it's a great program, it's just that I have a 5-year sub to NOD32.

Anyone else still experiencing this Sabnzbd/NOD32 problem besides me?

Re: Windows 7 memory leak

Posted: May 25th, 2010, 1:59 am
by shypike
Maybe this will help (quote from our ISSUES.txt file).
A bug in Windows 7 may cause severe memory leaks when you use SABnzbd in
combination with some virus scanners and firewals.
Install this hotfix:
Description: http://support.microsoft.com/kb/979223/en-us
Download location: http://support.microsoft.com/hotfix/KBH ... kbln=en-us

Re: Windows 7 memory leak

Posted: June 1st, 2010, 6:23 pm
by bluesk1d
I have what I believe to be this issue on Vista 64. I just installed the hotfix and I will test and report.

(Edit) So far my memory consumption has been normal and downloads through sab appear to be quite a bit faster as if my provider wasn't the bottleneck before. This hotfix is looking good for me so far...

(Edit 2) Confirmed - This hotfix resolved the issue for me.