Error in `/opt/emby-server/system/EmbyServer': double free or corruption (fasttop)

[blue-wizard 2]

Emby server crashed while playing an audio file.

 

I see the following in /var/log/syslog

Jan 19 15:39:05 raspberrypi emby-server[552]: *** Error in `/opt/emby-server/system/EmbyServer': double free or corruption (fasttop): 0x75118878 ***
Jan 19 15:39:05 raspberrypi systemd[1]: emby-server.service: Main process exited, code=killed, status=6/ABRT
Jan 19 15:39:05 raspberrypi systemd[1]: emby-server.service: Unit entered failed state.
Jan 19 15:39:05 raspberrypi systemd[1]: emby-server.service: Failed with result 'signal'.

And this is at the end of emby's own server log:

http://192.168.1.5:8096/emby/Audio/f08d94bb6148f792463f2f6e027ff8d2/universal?UserId=276f60239cab4b6cbd79114e50da4cd8&DeviceId=FCXIIW3zA1NiO84mrqjwzhSlaOCUjKqu1lzj0gywaN8&MaxStreamingBitrate=140000000&Container=mp3|mp3,flac,wma,wav&TranscodingContainer=ts&TranscodingProtocol=hls&AudioCodec=aac&PlaySessionId=1516378098954&StartTimeTicks=0&EnableRedirection=true&EnableRemoteMedia=false 
2018-01-19 15:37:44.730 Info HttpServer: HTTP POST http://192.168.1.5:8096/emby/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; MSAppHost/3.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Edge/15.15063
2018-01-19 15:37:44.775 Info HttpServer: HTTP Response 204 to 192.168.1.14. Time: 44ms. http://192.168.1.5:8096/emby/Sessions/Playing/Progress 
2018-01-19 15:37:54.752 Info HttpServer: HTTP POST http://192.168.1.5:8096/emby/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; MSAppHost/3.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Edge/15.15063
2018-01-19 15:37:54.805 Info HttpServer: HTTP Response 204 to 192.168.1.14. Time: 53ms. http://192.168.1.5:8096/emby/Sessions/Playing/Progress 
2018-01-19 15:38:04.774 Info HttpServer: HTTP POST http://192.168.1.5:8096/emby/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; MSAppHost/3.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Edge/15.15063
2018-01-19 15:38:04.824 Info HttpServer: HTTP Response 204 to 192.168.1.14. Time: 51ms. http://192.168.1.5:8096/emby/Sessions/Playing/Progress 
2018-01-19 15:38:14.794 Info HttpServer: HTTP POST http://192.168.1.5:8096/emby/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; MSAppHost/3.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Edge/15.15063
2018-01-19 15:38:14.841 Info HttpServer: HTTP Response 204 to 192.168.1.14. Time: 47ms. http://192.168.1.5:8096/emby/Sessions/Playing/Progress 
2018-01-19 15:38:24.807 Info HttpServer: HTTP POST http://192.168.1.5:8096/emby/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; MSAppHost/3.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Edge/15.15063
2018-01-19 15:38:24.853 Info HttpServer: HTTP Response 204 to 192.168.1.14. Time: 46ms. http://192.168.1.5:8096/emby/Sessions/Playing/Progress 
2018-01-19 15:38:34.834 Info HttpServer: HTTP POST http://192.168.1.5:8096/emby/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; MSAppHost/3.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Edge/15.15063
2018-01-19 15:38:34.883 Info HttpServer: HTTP Response 204 to 192.168.1.14. Time: 48ms. http://192.168.1.5:8096/emby/Sessions/Playing/Progress 
2018-01-19 15:38:44.849 Info HttpServer: HTTP POST http://192.168.1.5:8096/emby/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; MSAppHost/3.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Edge/15.15063
2018-01-19 15:38:44.895 Info HttpServer: HTTP Response 204 to 192.168.1.14. Time: 45ms. http://192.168.1.5:8096/emby/Sessions/Playing/Progress 
2018-01-19 15:38:54.865 Info HttpServer: HTTP POST http://192.168.1.5:8096/emby/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; MSAppHost/3.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Edge/15.15063
2018-01-19 15:38:54.907 Info HttpServer: HTTP Response 204 to 192.168.1.14. Time: 41ms. http://192.168.1.5:8096/emby/Sessions/Playing/Progress 
2018-01-19 15:39:04.896 Info HttpServer: HTTP POST http://192.168.1.5:8096/emby/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; MSAppHost/3.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Edge/15.15063
2018-01-19 15:39:04.936 Info HttpServer: HTTP Response 204 to 192.168.1.14. Time: 40ms. http://192.168.1.5:8096/emby/Sessions/Playing/Progress 

It seemed to occur just as it was beginning a new track.

I was unable to reproduce the error when playing the track again after the restart.

 

Any idea what this error means?

[Luke 42078]

hi there, can you please attach the complete emby server log? thanks !

[blue-wizard 2]

Yes, here it is: emby server log.txt.

[Luke 42078]

Ok, i haven't seen this before. I guess let's see if it happens again. I would update to the latest version.

[blue-wizard 2]

Happened again last night, from /var/log/syslog:

Jan 19 23:01:10 raspberrypi emby-server[558]: *** Error in `/opt/emby-server/system/EmbyServer': double free or corruption (!prev): 0x012da018 ***
Jan 19 23:01:10 raspberrypi systemd[1]: emby-server.service: Main process exited, code=killed, status=6/ABRT
Jan 19 23:01:10 raspberrypi systemd[1]: emby-server.service: Unit entered failed state.
Jan 19 23:01:10 raspberrypi systemd[1]: emby-server.service: Failed with result 'signal'.

Here is the emby log.

 

I will update to the latest version now.

Edited January 20, 2018 by blue-wizard

[Luke 42078]

Thanks. Let us know how you get on.

[juanmoura 0]

have the same problem. I'm using 3.5.2 in DietPi. I'm watching until 23PM but today around the 5AM stop with the same error.

[Luke 42078]

have the same problem. I'm using 3.5.2 in DietPi. I'm watching until 23PM but today around the 5AM stop with the same error.

 

Hi there, please attach the emby server log. thanks.

[GreatLord 1]

Hi 
I did run Emby-server frist on Dietpi for pine64. it seem thuse packages that comes with dietpi does not work well with Emby server or plex. 
random crash. I mange get same crash as you after only 60mins with Emby-server on dietpi. 

 

a another issue I got was dlna profile was not detect correct for LG TV or chromecast for plex server and emby server.

after 1 month debuging and so I decide change distro 

 

I love dietpi it works well for me in most case on Pi and Pine64, But I did change few days to Ubuntu 16.04 for PI and Pine64. 

 

I do not regeit it all. I manger get more stable both on PI and Pine64. 

 

 

[Luke 42078]

Thanks for the feedback.