Sonarr keeps shutting down

Help & Support
#1

Sonarr version (exact version): 2.0.0.5090
OS: Windows 10
((Debug logs)): https://drive.google.com/open?id=1OK77XtWGIpapPc_jIWNVeuYGtlG_yseQ

I am running Sonarr on my Windows machine and every so often, I’ll try to open Sonarr from the taskbar icon only to see that it suddenly disappears [which means it has stopped]. I go to my shortcut in the browser and open localhost and it still doesn’t open. So I have to click on the desktop icon to launch the application to get it to work again.

I looked at the logs [attached] and it shows a System.OutOfMemoryException: error. I have an i5 Windows 10 machine with 8GB which should be more than enough.

P.S. there are a bunch of other errors in there as well, and they pop up from time to time as well, especially the ‘JSON integer 18446744073709552000 is too large or small for an Int64’ but let’s stick to the main issue.

Any ideas?
Thanks

#2

You’ll need to enable ((trace logging)) and post those logs (your logs are just info logs, not even ((debug logs))).

It’d also be worth checking the other threads on the same subject: https://forums.sonarr.tv/search?q=System.OutOfMemoryException%20order%3Alatest as there are a few common causes of the issue due to software or hardware.

#3

Alright so I finally caught a session when it crashed with the trace/debug logs enabled. It crashes around 3am in the morning on the 6th.

Check them out here. https://drive.google.com/open?id=1FrPxCUpijuJjVcYapYUXyadDR1h4kXB-

I can’t see anything out of the ordinary but maybe you guys can see something?

In the meantime, I did some memory tests and memory checked out.

Thanks!

#4

Doesn’t look like Sonarr was doing much of anything at the time of the crash (though it was closer to 4am). It looks like the task was ended without an error, though it’s possible it was unable to log an error.

Does event log should anything around that time?
Might be worth starting NzbDrone.exe in a command prompt and seeing if anything is logged to the console when it crashes.

Why did you open another thread with the exact same logs?

#5

Sorry about the duplicate thread. Couldn’t find this one on the main menu.

I found an error in the Event Viewer at the time of the crash [03:51am, 6th Jan], about 6 mins after the final log entry [and yes, closer to 4am].

Faulting application name: NzbDrone.exe, version: 2.0.0.5090, time stamp: 0x5a318553
Faulting module name: ntdll.dll, version: 10.0.16299.64, time stamp: 0xac8afc81
Exception code: 0xc0000005
Fault offset: 0x0005d0bc
Faulting process id: 0x3850
Faulting application start time: 0x01d3857c6f36ad82
Faulting application path: C:\ProgramData\NzbDrone\bin\NzbDrone.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 55fdb118-dbc7-4151-9a19-19b8fbe256a1
Faulting package full name:
Faulting package-relative application ID:

  • 1000 2 100 0x80000000000000 27159 Application Upstairs-PC
  • NzbDrone.exe 2.0.0.5090 5a318553 ntdll.dll 10.0.16299.64 ac8afc81 c0000005 0005d0bc 3850 01d3857c6f36ad82 C:\ProgramData\NzbDrone\bin\NzbDrone.exe C:\WINDOWS\SYSTEM32\ntdll.dll 55fdb118-dbc7-4151-9a19-19b8fbe256a1

That’s all I got from the log.

#6

So I went over a lot of old posts and it looked like Bitdefender might have been the cause.

I added Sonarr to the exceptions list and it hasn’t crashed since my last post.

We should be good.

1 Like
#7

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.