I’m running Sonarr on a Raspberry Pi 2 running OSMC. Once in a while it gets killed and I have to restart the service. I just found the following error message in dmesg.
[132552.660385] Out of memory: Kill process 836 (mono) score 289 or sacrifice child
[132552.660404] Killed process 836 (mono) total-vm:300112kB, anon-rss:216544kB, file-rss:0kB
Any way to prevent this?
Depends what its doing when it gets killed off, but Sonarr wasn’t designed around running on a system with a total of 1GB of RAM.
Yeah I know I’m pushing the limits. Most of the time it seems to be during library updates.
Could try removing some larger series to see if that helps, if RSS Sync and library update trigger at the same time and there are a lot of indexers I can see that having an impact.
@markus101 I think I created a GH issue once to investigate performance requirements on Syno, so we can see what we could change/improve to adapt to low-spec systems better.
As we know it has nothing to do with .net/mono jitter taking cpu, since that’s just a one time cost. I’m mostly concerned with the memory pressure from the caches, so it would be interesting to see how much we actually use, both passively and during active task such as rss sync, series update.
Ideally we would want to have Sonarr adapt it’s logic and caching mechanism based on total system memory.
To tell you the truth I’d prefer to turn the RSS Sync off completely. None of my indexers have it enabled but it still seems to run (not sure if this actually uses resources or not).
Mostly I’m using Sonarr to manage my library. It’s great at showing missed episodes and renaming files. It’s also the only program that I know of that will clearly identify an Ended series.
Set the interval to zero then, but if you’ve disabled it at the indexer level it will just log that its unable to run.
Disabling RSS Sync will disable Sonarr from grabbing anything automatically though, you can still use the search functionality.
On my syno 412+ with 1gig ram mono/sonarr takes between 200-250 mb.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.