Alt.Binz forum
New Alt.Binz versions => Bugs => Topic started by: bis96gw on January 08, 2011, 09:18:01 pm
-
Setup is as follows :-
0.33.4 running on Windows 7 32-bit under Vmware Fusion 3.
If I have a primary news server (my ISP, small retention) with a backup news server astraweb, when retrieving an NZB, if alt.binz has to consistently go to the backup server for every article, it starts to leak memory. It keeps leaking until it gets to around 500Mb then it will repeatedly pop up an errror saying "Not enough storage to process this command" (there is lots of disc space available, so believe it's referring to memory rather than disk storage).
This only seems to happen when retrieving articles in this way i.e. if I change astraweb to be the primary server and download the same NZB, there is no leaking. So I can only assume consistently having to go to the backup server for articles is causing the leak.
-
How much time does it take to leak 500MB? Or better to say how many articles with whole process of connecting to backup. Cause I have similar setup and I'm having hard time reproducing it.
-
I will try and work it out. Since my connection went up to 30Mb/s, it defintely happens faster, so it probably is related to the number of articles and/or download speed.
-
Leaks at the rate of about 15MB per minute when downloading at 30Mb/s....
Looks like it's trying to release some memory as the amount allocated to altbinz.exe goes up and down, but looks like it can't do it fast enough, so it eventually reaches the 500MB mark and dies....
-
Do you have articles caching on? If yes, could you please try without it.
-
Do you have articles caching on? If yes, could you please try without it.
No, didnt even know that feature was there, it's set to 0MB
-
I tried setting the cache to 200MB and that looks like it will fix the problem - the amount of memory used rises rapidly, but then drops back down to around 70MB (after it has written an article to disk I presume?).
-
I thought it had, but the cache hasn't solved the problem - it still leaks memory and then hangs onto it afterwards....
Could this be related to the fact alt.binz is running on a VM under vmware?