by Valmont » Thu Feb 05, 2015 7:52 pm
It's version 6.55. It started with a total download size of about 1.5 TB, all downloads of 1 GB up to about 40GB. So relatively not many files in the queue. Next morning it had about 1 TB left as the SSD disk of 500 MB was full. I cleaned up resumed the download after a restart.
Next step I did was deleting stuff from the download list as it become apparent what I didn't need or want to download. All works fine.
When having about 500 GIG left a few hours later, I checked Newsbin to see what else is left to download.
Noticed slow reaction time (4 seconds) when clicking things. Checked the CPU load. It used 15%. That only happens when it unpacks stuff. But nothing was being unpacked! And even if it does. the UI still responds fast normally. So I knew Newsbin was doing activity out of the order. Checked also the DISK performance but nothing was in the queue related to Newsbin and Disk "E", which is the SSD dedicated to Newsbin.
So I shut down Newsbin. But the process didn't unload from memory and it started to use up the memory up to 10GB. Then it generated the Out of Memory error even though I have 6 GB left. And that's that. So I rebooted the PC. Resumed the download, and everything right now is fine and dandy. Shutdown works fine, it unloads itself from the memory.
I noticed this odd behaviour twice before since I have this fast 90MB usenet connection (fully utilized) and replaced my very old HDD with a SSD (Samsung 840 Pro). Downloading a TB or more is nothing new for me. Before I go to work, I select stuff from top to bottom, then when I go back home I select and delete 99% again. I do this since Newbin 4. It looks like it can't handle extreme usage and various kinds of speeds.
Cheers!
Edit:
Downloads complete in 7 hours. Maybe I can just delete this dreaded database? Which one would it be?. First I finish downloads. Then I quite newsbin. If it unloads correctly (I'm sure it will), then delete database?