Win764bit 64bit-NBP6.40 bld2057 Memory Crashes

[SusiBiker]

NBPx64 v6.40, 2057 on Win7x64Pro
Dual-Core Pentium 1.8GHz, 2GB RAM, 5GB Swap.
(Before anyone says this is PC is underpowered, NBP was working fine until this release was installed.)

Hi guys. Was wondering if you have any ideas...?

I am regularly coming back to my computer and finding that it has crashed through lack of resources.
Here is the report from the Event Viewer (25/09/2012 23:59:26) -
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: newsbinpro64.exe (4964) consumed 6888144896 bytes, Skype.exe (2604) consumed 94285824 bytes, and dopus.exe (4468) consumed 81899520 bytes.

As you can see, NBP64 is using *6.4GB* of memory!

Here's another (24/09/2012 00:42:07) -
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: newsbinpro64.exe (1648) consumed 5526913024 bytes, firefox.exe (3920) consumed 223358976 bytes, and ImgBurn.exe (3972) consumed 125259776 bytes.

5.5GB this time.

This has only happened since installing this release. Sorry, I can't tell you what version I was using earlier, but it was a beta version. Maybe two or three versions before this...?
I'm using AutoPAR and AutoUnRAR. I was before and had no problems.

Any ideas where to look/what the problem might be...?

Thanks,
Susi xx

[Quade]

Answered you over email.

How much RAM do you have? 6 gigs, while alot shouldn't be enough to take your PC down.

[itimpi]

It could as it was stated that there was 2GB of real RAM and 5GB of swap space available.

I guess the real question is what is causing this amount of memory to be consumed by Newsbin in the first place? I have never got Newsbin over the 1GB mark in normal usage (albeit I do not use headers with very large groups).

[SusiBiker]

Hi itimpi,

I left it going last night with all the Performance Options ticked for a Low-Powered PC. Wasn't any ISOs in the list, so I don't know if they were causing it to crash. There were a lot of files that when assembled were about 300MB. 848 of them using around 163MB. The Cache hovers around 84/100, diving down very low for a few seconds, when a decode takes place.
I have some suspect files that were showing IO errors. I'm going to try to DL them again to see if that is what is causing the crash. There is no problem with my HD going missing - there are no reports of that in the Windows Event Viewer.