Build 4163 (64 bit) memory not released

[Lord_Malebolgia_666]

Newsbin does not release the memory once the tasks are completed.
With each task it keeps hogging more memory until nothing is left.
System and Newsbin are running 24/7.
First time for me that happens, all prior versions did not have this problem.
Newsbin has to be exited for the memory to be released.

[Quade]

There were some other reports of something like this. A clean re-install seemed to fix it for the people who had the issue. It was never clear what the problem actually was.

I've been running all night long and it's sitting at 200 megs of memory usage.

[Lord_Malebolgia_666]

Thank for the advice, will try the clean install, although the other similar problems, i think, were the database hogging massive harddisk space.

[Lord_Malebolgia_666]

I have done a clean install but the "not releasing memory" issue has not gone away , the private memory stack of the executable is 3 gig a.t.m. and still rising , it just doesn't release the memory after its done with its task.

[Quade]

It's not a question of releasing memory. It shouldn't be using that much at all. Running normally with a normal cache of 200 I wouldn't expect it to go over 250 megs.

The only thing that should use RAM is loading up headers into a post list. Even then, 3 gigs is a bunch of headers. If you use NZB's or search for downloads. Memory use should be minimal.

[Lord_Malebolgia_666]

I use mainly NZB's for download haven't used Header donwloads at all in this clean install.
The Private mem of newsbin is 3.5 gig now and the sharable mem is 34kb.
System allocation mem for newsbin was set to 4.2gig by OS.

When i start newsbin and leave it with nothing to do it behaves the way u described with a low memory footprint.
The instant i start a download it increases private memory but does not give it back after download, par & rar is done.
With each download and the subsequent par & rar task private mem increases.
The Newsbin data directory is only 553KB a.t.m. and is located on a diffrent drive as the Newsbin program folder.
Due to the fact that prior versions didn't have this problem, something should have changed with the memory allocation.

on a diffrent note :

Newsbin performs and behaves very good and fast with the exception of the above. Image link not allowed for unregistered users
Just to let u know that i appreciate your efforts on the development on this program .
Been arround here for quite some time , think since version 3.xx

[Quade]

What happens if you hit "Help/About". How much memory is freed?

[Lord_Malebolgia_666]

I started newsbin fresh, had a private mem of 543MB

Started a download about 10 gig.

Private mem went up to 697MB

Clicking on "about" brought it back to more or less 543MB

[Quade]

I started newsbin fresh, had a private mem of 543MB

You're in bad shape even just starting up. I start Newsbin and it's using 18 megs. How much do you have in the failed and wish lists?

[jackholexxxx]

Mine starts at ~25MB but grows to ~850MB within a few hours. Just normal header download on 11 groups. I don't keep headers around, I delete them after viewing. Went to Help-> About and the memory dropped to 65MB.

[Quade]

About and the memory dropped to 65MB.

Sounds like you have a large cache. About 800 megs worth of cache. Help about clears the cache.

[Lord_Malebolgia_666]

I have been running newsbin for 48 hours and given it no tasks to do, just waiting.
Private memory usage increased from 500MB to 2599 MB, at this point clicking help/about
released nothing.

After i started a NZB download task private memory increased from 2599MB to 2678MB but could be lowered again with clicking
help/about to 2589MB.

I can't pinpoint what newsbin is doing during the wait time that is slowly increasing private memory and
why it's not given back that memory after being idle for some time.

I Haven't mentioned it but i am running Win7 pro 64 bit.
When i looked at the compatibilty modes that can be used i noticed the windows 7 option
As i started newsbin in that mode it started with 53kb private memory.
I am gonna let it run for a few days and see how memory consumption gets handled.

[Quade]

I Haven't mentioned it but i am running Win7 pro 64 bit.
When i looked at the compatibilty modes that can be used i noticed the windows 7 option
As i started newsbin in that mode it started with 53kb private memory.
I am gonna let it run for a few days and see how memory consumption gets handled.

Could you clarify what you actually did here? Sounds like the problem might have nothing to do with the downloading parts of Newsbin but is instead related to the display parts.

[Lord_Malebolgia_666]

I went to the newsbin icon on the desktop , clicked properties and went to the compatibility tab and set the compatibility mode to windows 7 .
started with 53kb private memory.
now 2 days later, (newsbin was completely idle in those 2 days) private memory increased to 5,2gb occupying all the free ram available in the system.

[Quade]

Had this happen to me last night. Was fine before I went to bed. Woke up and checked and it's sitting at nearly 2 gigs. It was idle all night long.

I'm trying to figure out what's happening now. It seemed to happen while the screen saver was up. I'm wondering if it's not in my code but in the library that handles all the display stuff.

[Lord_Malebolgia_666]

Good to know you could duplicate the problem, I hope you can fix this.
Thanks for the support Image link not allowed for unregistered users

[Quade]

In the options, could you check if "Remote Control" is active? If it is disable it and restart Newsbin. See if it acts the same.

[Lord_Malebolgia_666]

Looked it up in options ,Remote Control was not enabled

[Quade]

Thanks for the feedback. I'm looking at it.

[Lord_Malebolgia_666]

I upgraded to 6.61 B1 build 4195 (64 bit) to see if my problem migrated to to this version.
It did .

[Quade]

I've found a way to make it consistently go crazy. If I load a large group and do a bunch of "delete all posts by poster" ram use will start climbing with no limit.

It only happens in the 64 bit version so, you could run the 32 bit version, they're functionally identical.

[spg]

I just upgraded to 6.60 and found windows complaining about no memory about 2 hours after a simple queue download. No groups openned or anything else. After 2 hours memory usage had grown to 9.4gb before everything eventually crashed.

On restart, memory quickly hit 1GB (within 2 minutes) and continues to grow. A fresh install does nothing, 6.61b3 does nothing and help/about doesnt seem to do anything later.

Memory grows by about 1MB/sec, about twice my download speed

6.60 is totally unusable for me now Can I please get a 6.55 download link?

[Quade]

All the versions are in the download page.

Thankfully it only seems to be a couple of you guys having this problem. If you want to try again, I'd wipe out the "Import" folder in the data folder. Then start and see what happens.

[spg]

a rollback to 6.56 has fixed the memory leak for me. I guess I'll be staying here for a while

[spg]

The Import folder was empty

[Lord_Malebolgia_666]

I upgraded today to Win 10 64 bit.
Newsbin is running for 6 hours now, memory footprint 78kb, keep yer fingers crossed Image link not allowed for unregistered users

[Quade]

Yeah I'm pulling my hair out over this.

78 kb is pretty much impossible. Not sure where you're seeing that but 25 megs should be normal when you start up and 250-300ish when downloading. If you've increased the cache from 200 to a larger number, you can assume 1 Mb per cache block so, 200 = 200megs. 2000 = 2Gigs.

[Lord_Malebolgia_666]

This is what windows resource monitor displays:
newsbinpro64.exe pid 816 - commit :1.930.220 Kb - working set 266.285 Kb - shareable 128.234 Kb - private 140.284 Kb

Its stable for the last 24 hours

[Quade]

Good, and weird...haha.

I've thrown some circuit breakers in and made some slight changes in order to reduce RAM use but haven't found any smoking guns. What changed do you think to make it stop using RAM?

[Lord_Malebolgia_666]

Curiously the only thing i changed was the OS, upgraded from win7 64bit to win10 64bit.
Now it seems the commited memory is growing instead of the private mem, but in a very slow rate.
But i guess that is not a problem.

Win10 64bit works like a charm for a.t.m. Image link not allowed for unregistered users

[Quade]

Thanks.