NZBGET Out of memory issue

Sonarr version (exact version):
.net Version:4.8.0
AppData directory: C:\ProgramData\Sonarr
Startup directory: C:\ProgramData\Sonarr\bin
Mode: Tray
Uptime: 1:04

Mono version (if Sonarr is not running on Windows): Tray
OS: Windows 10
Debug logs:

Description of issue: Error shows that the Sonar can not get to my Download client. Memory Issues.

Have tried to stop Sonnar and restart and then put it in debug mode. Just got the latest update, that is the only change that I am aware.

Additional Information:
I am seeing out of memory issiues when I look at the log files. I get the same on Lidarr but Radarr is fine. It has gotten files as late as earlier this morning, but nothing has changed on my system that I am aware.

Debug log file:

And jus like that, the issue just dissapeared. I do not know why or how, but in the past 10 minutes or so, the issue just cleared itself up. Sorry for any inconvience.

1 Like

And is back again today. So, could this be an issue with the current version of Sonarr and Lidarr and Radarr is fine. as I have things downloading with NZBGET, right now, but Sonarr and Lidarr see it as not available and Radarr is fine and using it.

In the past out of memory errors have been seen due to memory issues at the hardware level, the first thing to do would be run a memory test (outside of windows), such as to see if there are any errors brought up there.

I did a check of my memory and everything was fine. I decided to re-load NZBGET and use the latest stable version not the latest beta version. Now I get a new issue.

Also, one thing I do see both before and now on both Sonarr and Lidarr (but Radarr still works fine) is that they send the request to down load the file to NZBGet, it downloads the file, says it has done the post work, but the file name is not correct, and Sonarr and Lidarr both never get the file and import it.

It looks Sonarr is unable to get the queue/history from nzbget due to the same issue it wasn’t able to add it (OutOfMemoryException), is Lidarr running into the same issue?

Do you have a large queue and or history in nzbget currently?

Yes, both Sonarr and Lidarr have the issue. Radarr does not. Let me check the history. You are right that I could have a large amount of history in the nzbget client. Let me look at that.

Enabling Remove in Settings->Download Client->Completed Download Handling would help with history.