newsbin.com

Using version 6.11, build 1342 on Windows Server 2003 R2 SP2 32-Bit.

I've encountered an issue which you might find interesting. I've been attempting to download a set of files, but no matter how many times I try, logging keeps reporting the same "thread crash" errors. Here's a sample:

Ideas?

Yeah, don't post what you're downloading.

You're running 32 bits meaning there's the potential you're running out of address space.

- Did you enable the /3gb switch to allow newsbin access to up to 3 gb of address space? I don't know if your OS actually needs it though (meaning it might be on by default).

- What are you downloading too? Regular drive, NAS or something else?

- How much RAM is Newsbin using when this happens?

I've been doing all my testing 32 bits lately but, because I'm running Win7-64. Even 32 bit apps get access to > 3 GB or RAM.

Oop, thanks.

- I did not enable that switch - I will.

- Downloading to regular SATA drive, 457GB free.

- Newsbin is currently taking 934,260K of memory, with a VM size of 1,107,464K. However, Windows reports that only 1620M of 3944M is in use.

Strange, though. Of the 10 files in this series, the first 3 downloaded without issue. Only the remaining 7 started generating these errors. And now, no matter what I try to add to the queue, regardless of size, I get the same errors.

The damage might have been done already. I assume you've restarted at least once.

So, you're running Newsbin inside a VM then? That's unusual in itself. Are you downloading to an internal driving using "VM" sharing? If yes, you might try downloading to the VM local drive and see if this problem goes away. I've seen VM sharing not work very well.

Sorry, I wasn't clear. By VM, I meant Virtual Memory, not Virtual Machine. If I understand correctly, it's the Windows way of saying memory + swap.

Got it.

I rebooted the server and added the /3gb switch, and have since been able to successfully download the files. I can't be sure which of the two actions, specifically, did the job, but there you go.

Thanks!