Constant crashes on raspberry pi

[Karajorma 6]

So having failed to get a stable Emby setup on either Bananian or my QNAP I decided to give Emby one last try on my Raspberry Pi 3 which is running OSMC. Unfortunately it's not proving any more stable there. It seems to crash out every few hours.  Using systemctl reported back this

 

 

Loaded: loaded (/usr/lib/systemd/system/emby-server.service; enabled; vendor preset: enabled)
   Active: failed (Result: signal) since Fri 2018-09-21 17:23:52 HKT; 31min ago
  Process: 303 ExecStart=/opt/emby-server/bin/emby-server (code=killed, signal=ABRT)
 Main PID: 303 (code=killed, signal=ABRT)

Sep 21 15:31:11 Skeleton emby-server[303]:       NUMBER_OF_BYTES-eng: 29390766
Sep 21 15:31:11 Skeleton emby-server[303]:       _STATISTICS_WRITING_APP: mkvmerge v7.8.0 ('River Man') 32bit built on Mar 27
Sep 21 15:31:11 Skeleton emby-server[303]:       _STATISTICS_WRITING_APP-eng: mkvmerge v7.8.0 ('River Man') 32bit built on Ma
Sep 21 15:31:11 Skeleton emby-server[303]:       _STATISTICS_WRITING_DATE_UTC: 2015-05-05 06:49:50
Sep 21 15:31:11 Skeleton emby-server[303]:       _STATISTICS_WRITING_DATE_UTC-eng: 2015-05-05 06:49:50
Sep 21 15:31:11 Skeleton emby-server[303]:       _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
Sep 21 15:31:11 Skeleton emby-server[303]:       _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
Sep 21 17:23:52 Skeleton systemd[1]: emby-server.service: Main process exited, code=killed, status=6/ABRT
Sep 21 17:23:52 Skeleton systemd[1]: emby-server.service: Unit entered failed state.
Sep 21 17:23:52 Skeleton systemd[1]: emby-server.service: Failed with result 'signal'.

 

And here's the end of the log for the last crash

 

https://pastebin.com/nXKCFxCb

[Luke 37112]

Hi, can you try turning off the servers dlna features and see if that helps? Thanks.