Version 6.73 Beta 3 Available...

[dexter]

A few more bug fixes are in B3:

Summary:

• Made change to Sonarr integration when reporting status, now only reports one line per NZB representing the largest files.
• Added DNS caching as emergency backup for normal name resolution. If resolve fails, the cache is consulted.
• Fixed issue using Ctrl-R on posts with obscured subjects.
• Modified filename mode to strip any formatting chars off the begin and end of the cleaned subject.
• Made changes to AutoPAR to make sure PAR files are assigned to files if they are added to the download list later.
• Made change to make sure "Storage Age" doesn't apply to NZB files. Should only apply to header storage.

The download link is on the Newsbin Beta Page. If you find any issues, please reply to this thread or use our Technical Support Contact Form.

[Eurisko]

I do notice the memory usage of Newsbin creeps up and doesn't seem to let go. My Newsbin has been busy this week, but it was sitting idle this morning and I noticed it had creeped up to 1.6 gigs of memory usage. Why doesn't it return back down? I've noticed this several times in the last week. Restarting it drops it's usage back to 40megs or so. Just curious.

[Quade]

32 bit or 64? How do you normally download?

[Eurisko]

64 bit, Windows 10.

Typically I leave Sonarr to do the work. I have also done a lot of manual downloading from results in the search. This week has been abnormal for my regular Usecase which is mostly Sonarr.

When I posted my last message, I had literally just restarted it. It's idle now, and I just looked and it's up to 815 megs used.

Since the restart, it looks like only one item was downloaded via Sonarr.

EDIT: Restarted it, usage went back to 40~ megs. Downloaded one 10 Gig file. It did a par repair, then decompressed it. Cache was at 756/1000 (it's done this for a few versions where it doesn't release the cache and I have to do the Help About or Restart it to clear it out.). Memory was at 680 megs and never returned to normal.

[Quade]

Cache was at 756/1000

This is where a gig of your memory usage is going. By setting the cache to 1000 you're telling Newsbin it's OK to keep 1 gig of ram around to use. I only use a cache of 200 these days. A large cache doesn't buy as much as it used to because you can set it to download and unrar at the same time.

[Eurisko]

That makes sense about why it uses that much. I just didn't understand why it doesn't release that memory when it's done. (Or clear the cache back to 1000/1000).

[Quade]

When you tell it it can use 1G it says "fine". It makes no effort to give that RAM back to the OS.

As for the records that don't get purged out. Eventually those blocks of memory would get purged out or re-used. There's no reason to purge the data unless it's necessary and it's only necessary when it runs short.

You're trying to apply some functionality that just isn't there. Not going back to 1000/1000 isn't a bug it's kinda...nothing. Because the RAM isn't freed in normal operation anyway.

You can force it to flush with help/about but, that just means Newsbin will re-allocate the RAM next time you download.

[cage]

Does "Read Post Body" ie CTRL-R work for anyone? All it does is place a text file in the 'Read Posts' directory and never displays it. This has been broken for me for a very long time now and still doesn't works in 6.73 Beta 3.

[dexter]

Works for me. Wonder if your windows association for .txt files got messed up? Newsbin will launch whatever app is associated with .txt files. If there is no association, it won't do anything.

[redive]

I have been using the latest RC for a while with no issues. A couple of days ago when loading a large group, NB bogged and eventually crashed. Watching the memory usage, it is basically going up until NB has used all 8gb of ram. Not sure why this is suddenly a problem. Suggestions?

[redive]

The other issue with this that I forgot to mention is that group loading is extremely slow. In the past this has not been the case.

[dexter]

This is due to Usenet getting spammed. Upgrade to the latest beta, 6.73 Release Candidate 2, then follow these instructions: http://help.newsbin.com/index.php/V673-FilterDownloads

[redive]

This is due to Usenet getting spammed. Upgrade to the latest beta, 6.73 Release Candidate 2, then follow these instructions: http://help.newsbin.com/index.php/V673-FilterDownloads

Thanks! That had crossed my mind. Will try that out.

Mark

[redive]

This is due to Usenet getting spammed. Upgrade to the latest beta, 6.73 Release Candidate 2, then follow these instructions: http://help.newsbin.com/index.php/V673-FilterDownloads

I generated the filter using the instructions you provided. I added the filter in the group properties dialogue. However, the name of the filter is not showing up in the filter profile column next to the group. Am I doing something wrong?

Thanks,
Mark

[dexter]

It's not supposed to show up there. As long as it is listed in the Properties page for the group under Header Filter then it is installed properly. The other location you are referring to applies the filter when displaying headers from the database. What we are suggesting is you apply this header filter that keeps the spam from getting into your header database on your hard drive in the first place.

[redive]

It's not supposed to show up there. As long as it is listed in the Properties page for the group under Header Filter then it is installed properly. The other location you are referring to applies the filter when displaying headers from the database. What we are suggesting is you apply this header filter that keeps the spam from getting into your header database on your hard drive in the first place.

Got it. Thank you.

[redive]

It's not supposed to show up there. As long as it is listed in the Properties page for the group under Header Filter then it is installed properly. The other location you are referring to applies the filter when displaying headers from the database. What we are suggesting is you apply this header filter that keeps the spam from getting into your header database on your hard drive in the first place.

That works great! Thanks for the solid support.

Mark