Alt.binz memory issues Win 7 x64

[pcbilski]

Hello.
I have searched the forums and can't find anything relating to this issue, hope it isn't covered somewhere else.
As stated above using Win 7 64 bit Ultimate, Alt.binz 0.33.4 and Eset Smart Security.
Since the earlier version of alt.binz I have had an issue with memory leaks. The more I download, the quicker my available RAM gets used up until my PC slows to a crawl with nearly 100% physical RAM usage.
There is no account for the usage in task manager and when alt.binz isn't open it doesn't occur and when I'm downloading less it happens more gradually.
I have a feeling it might be an issue with par2 because it seemed to do it with another client as well, but didn't do extensive testing so can't be sure so I thought I'd ask here.
Can anyone shed any light on this?
If any further info is needed please let me know, really want to get this sorted out because I love the client (great work btw) and can't bear using anything else.
Thanks in advance.

[pcbilski]

OK, well no one seems to be having the same issue.
There is a hotfix for Win 7 x64 that will hopefully fix this, it can be found here:
http://support.microsoft.com/kb/979223/en-us

[pcbilski]

Ok, confirmed the hotfix does resolve the issue.
Hope this helps someone else.

[pcbilski]

Well, after a reload on my new hardware I am having this issue again and am unable to install the hotfix saying "the update is not applicable to your computer".
Anyone have any ideas?

[Hecks]

I'm pretty certain that Alt.Binz doesn't use anything from Windows Filtering Platform, so I've no idea why that hotfix worked and I guess nobody else does either. 

On the other hand, the KB mentions that "WFP callout drivers are usually used in third-party antivirus and firewall programs", so it seems sensible to start there: completely disable any firewall & AV temporarily and see if it fixes. Otherwise look at your networking card & drivers.

[pcbilski]

I'm pretty certain that Alt.Binz doesn't use anything from Windows Filtering Platform, so I've no idea why that hotfix worked and I guess nobody else does either. 

On the other hand, the KB mentions that "WFP callout drivers are usually used in third-party antivirus and firewall programs", so it seems sensible to start there: completely disable any firewall & AV temporarily and see if it fixes. Otherwise look at your networking card & drivers.

Thanks for the reply.
I do think it has something to do with Eset Smart Security/Nod32 Antivirus, I have read other forums with people having similar issues with other nzb clients as well.
Don't really feel comfortable disabling my anti-virus and also don't want to switch to another package.
Have a new board, so new NIC and drivers and same issue as on old system.
Guess there is no alternative but to just restart every few days.
It was working perfectly with the hotfix before, same OS. No idea why it won't install now.

[Hecks]

As I said, disable AV & firewall *temporarily* to see if that fixes your problems.  Without knowing the source, there's not much that can be done.

Look particularly in your AV settings for any NNTP traffic scanning and try to disable that; exclude all Alt.Binz folders from scanning, etc.

[pcbilski]

Problem with disabling it is that it takes several days for the RAM usage to creep up, depending on article size etc. but I guess I have to give it a try, have already added some exceptions to see if it helps.