Epic fail disk i/o error

[snupple1]

Sonarr version (exact version): 2.0.0.4204
Mono version (if Sonarr is not running on Windows):
OS: Win 10
((Debug logs)) (posted to hastebin or similar): http://pastebin.com/5N2D7NqT
Description of issue: Disk I/O Sqlite error on launch - Been getting these errors a lot recently and usually I restore a backup and everything is fine, but now no matter what backup I use I get the same error

[Taloth]

How’s your free disk space? and what kind of drive do you have?

[snupple1]

Thanks for the reply - That drive is a SSD and there is a bunch of free disk space… 35gb+

[snupple1]

Had a bit more of a look and there are a lot of Out of Memory errors:

http://pastebin.com/BevKSzhV

[snupple1]

Deleted a bunch of series and it seems to be ok now

[snupple1]

OK, back again…

Im still having issues with crashes every 2-3 days… The Sonarr log will say OutofMemory, the pc it runs on should have about 4gb of memory free…

This is a section of the log where the failure happens

http://pastebin.com/v4CZ27hX

This is the whole log:

http://pastebin.com/guq1ndzb

I have checked the windows event log and there is nothing of interested in there …

Debug log:

http://pastebin.com/PgbDrtfZ

Trace Log:

http://pastebin.com/HbyYdL3n

Any help appreciated

[markus101]

Looks similar to another user’s issue:

Sonarr Crashes on Windows (NzbDrone.exe error with clrjit.dll)

Sorry for the delay, lots to sift through (way more and a minute or two) and I wanted to discuss it with another dev. The fact that it dies during an RSS Sync is a symptom, not the problem itself, it just happens to be the time when memory is allocated and it becomes too much for the process. We had a few theories we tested out, but they didn't appear tot be the cause. We're going to need to capture a memory dump when Sonarr is running to see what information it can give us: You'll need t…

We’ll need the same information from procdump.

[snupple1]

OK, so I did that and this is what happened:

[markus101]

Was Sonarr shutdown for another reason, either manually or for an update?

[snupple1]

Not sure, so I did the procdump again and this is what happened.

I also created a Data Collector Set for Perf Mon to check that memory isnt going low and it seems fine around the time of the crash

NZBdrobe crashed like this and procdump was still running and exitted when I clicked on “Close this program”

Sonarr.trace.txt
http://pastebin.com/xyHKtUQa

Sonarr.dump.txt
http://pastebin.com/WxMa8bRG

Sonarr.txt
http://pastebin.com/g1Eqm75s

[snupple1]

@markus101: any ideas?

[markus101]

I also created a Data Collector Set for Perf Mon to check that memory isnt going low and it seems fine around the time of the crash

The issue likely isn’t the system running low on memory, but Sonarr using more than it’s allowed to, though it’s crashing without hitting the procdump limit.

16-9-1 12:52:36.3|Trace|Owin|SQLite error (5386): os_win.c:36454: (8) winShmMap3(C:\ProgramData\NzbDrone\nzbdrone.db) - Not enough storage is available to process this command.
 
16-9-1 12:52:36.3|Trace|Owin|SQLite error (5386): disk I/O error

Is Sonarr’s memory usage increasing over time?
Could you try a procdump with a smaller threshold, 250MB instead of 1000?