SABnzbd Forums

Hi, I have had windows 7 since it was beta and now I am using win 7 rtm with eset smart security.

I have been using newsbin to download stuff with for years and it has never faulted me, I decided for the first time yesterday that I would look into using SABNZBD, I like the look of it and what it can do, after hooking upto my buds private service, I liked what I saw and decided to put it onto my own rig, really great piece of software IMHO but after a few hours use it steals all my memory and forces me to reboot.

I have read the posts saying that it could be an AV problem, now I am using eset smart security,  the other threads I have read regarding this problem also remark about eset, but the thing is, I have been using eset smart security for years without problem and been using it since win 7 was beta, also without problem and then onto RC and then RTM, all the while using eset SS with newsbin, not once did I get that memory error.

I only started getting the error last night after say 4 or more hours of downloading using sabnzb and then the same today, to me the logical answer is that its sabnzbd thats at fault, because the problem only started after I installed it, ok I do understand that some will say that its probably eset, but if it was eset, which it may well be, but if it is, then why did I have no problems at all for years with newsbin downloading the very same binaries ? then for eset to mess up whilst downloading the same files but with sabnzb instead ?

I am desperate to use sabnzbd and I would love to know if there is fix or even talk of a fix, I am new to sabnzb so I dont know what all has been done regarding this issue if anything, but I would love for me to be able to use it without having to sacrifice eset, as that isnt an option.

I have after reading some posts, i have disabled web scanning for localhost, basically thats the only thing I can do without resorting to not scanning specific ports i.e 8080 or disabling webscanning altogether and even if I did disable that, some people said that it still didnt cure the problem, even moving to another AV product didnt cure some peoples problems.  I will have to wait and see if my attempted solution does the trick or not as I have just this second implemented it.

So my question is, does anyone have anything other than a guess asto what exactly is causing this problem and if so, do they know if there is a fix or if there is an upcoming fix ?

I am using the latest non RC version of SABNZBD.

If need be I can list all sabnzbd settings and also list the appropriate firewall/AV settings if they are needed.

I would really like to change to this from newsbin but at the moment it isnt an option til I can find out a way to stop it from using up all the memory.

Thanks in advance for reading and for any help that you maybe able to provide.


e.s

We've had several reports about problems in combination with eset.
Since a security suite is supposed to be transparent, we obviously blame eset.

It would be absurd if we had to modify SABnzbd because of some security suite.
In fact we don't have even have a clue about what we should change.
There are dozens of security suites that have no issue with SABnzbd.
Consider filing a complaint with eset also.

Hi Shypike, thanks for replying, I wasnt complaining, although it maybe came across as that and I am sorry if you understood it as that, I was basically just asking if there was any fix in the works etc.

I had read previous posts/threads and alot of them mentioned problems with eset, so I do understand that eset is maybe interfering with the sabnzbd or vice versa, but its weird, for years I have been dloading from usenet with eset and using newsbin and everything has been ok and then this happens, when its basically doing the same thing as newsbin is doing.  The thing that did make me curious was, the people who had the same problem as myself and who had eset, when they uninstalled eset the problem remained, when they uninstalled all AV apps, it still persisted, and others said by doing X or Y in eset fixes it, yet others say no it doesnt, so I dont know what to think.

Its just crap that it has happened as I have just paid for 2 more years of eset, 6 days ago I topped up and I aint giving it up anytime soon, yet I am DESPERATE to use sabnzbd. Had I known I would of probably dumped eset and continued to use sabnzbd and just use MSE for AV.

What I did notice was, it wasnt sabnzbd that took up all the memory, when checking which application was using all the memory, none were, they were all using there usual amounts, yet 3 gig of spare ram was being used by something as it was missing, what was using it I dont know ? as the total amount of ram used by the programs in the list just didnt add up to anywhere near 4 gig.

I will contact eset support and ask them if they have any thoughts about the situation, its likely they wont give a fcuk and will probably say its sabnzbd's fault and will probably redirect me back to your support, you know how it goes.

I guess I can install it on a spare xp box in the meantime til I get this prob sorted.

As I say, with what I have seen of sabnzbd so far, it is exactly what I need, as I spend far too much time pissing about downloading and setting things up regarding usenet and I would like most of it to be automated and your app does exactly what I want to do, hence me being desperate to use it and dumping newsbin pro.

Once again, I am sorry if you took my post as me complaining as it wasnt meant like that, I will contact eset support and if they have anything worthwhile to say I will get back to ya and let you know what they think the problem could be.

I tend to overreact when confronted with SABnzbd issues outside my control.
I'm especially frustrated by "security" suites and I personally
rely solely on Microsoft's anti-virus and firewall solutions, combined with common sense
(and NoScript on Firefox).
I think most security suites causes more problems than they solve.

I'm very reluctant to spend time on this. There are just too many security suites.
But more important: such a suite must be invisible for approved applications.
Our software needs to comply with the Windows API and Microsoft guidelines
and need not be modified to accommodate the quirks of a security suite.

That other programs do not have the same problem with eset is no surprise,
there are dozens of ways to handle socket communication all within the rules.
Our method is largely determined by the Python communication library.
Besides, it need not even be socket communication, but memory and disk usage patterns too.
Have you told eset to stay away from SABnzbd's working folders?

For your comfort: the official binaries for SABnzbd are created on an isolated
box and not on my daily work system.

Hi Shypike,

I contacted eset, this is what they said;


Good afternoon,



Can you please try excluding SABNZBD from scanning by ESET.



Exclusions.bmp  = Just a picture showing where the exclusion part is in there settings.



If this does not work then please can you send me export of ESET Settings and a sysinpector log. All this can be performed from within the ESET Software.



This will enable our developers investigate the issue further and come up with some possible solutions.



Many thanks.

------------------------------------------



I already added the exclusions after reading this site yesterday, so I will now send them a sysinspector log and a log of the Eset settings, I will get back to you with what they say once I get a reply fom them.

Cheers

es

Hi again Shypike,

I have just found out that it is not an Eset problem but it is infact a Windows Vista / 7 and Server 2008 problem.

MS have released a hotfix for it, soemthing to do with the WFP call out driver.

Here is the hotfix for those systems

http://support.microsoft.com/kb/979223/en-us

and this is a direct link to the hotfix

http://support.microsoft.com/hotfix/KBH ... kbln=en-us


Once installed, the problem was cured for me, memory usage is back to what it is normally like

Hopefully if any other people post regarding a similar problem then this hotfix might work for them ?

Cheers

es

So it turns out that both eset and SABnzbd are innocent.

Thanks for the feedback.
How weird that the patch isn't just in the monthly patch cycle.
I'll include it in the known issues list.

Yup, by the looks of it both sabnzbd and eset are not the cause, so alot of people can rest easy knowing that neither eset nor sabnzbd are the root of the problem.

For me the memory problem only showed its face after I installed sabnzbd, and I put 2 and 2 together and as usual came up with 5  and kinda blamed sabnzbd as being the problem, which it DEFINETLY was not 

I came across this thread over at the msdn forums that got the whole thing rolling;

http://social.msdn.microsoft.com/Forums ... 1ecc7f59cc

and this one at technet

http://social.technet.microsoft.com/For ... 154b9acff0


I have now dumped newsbin pro and am in the middle of a whacking great download using a lovely stable sabnzbd 

Cheers

es