EmbyServer crashed with "double free or corruption (fasttop)"

[mrsimo 0]

The process crashed in the middle of playing a video via DLNA from my PS4. I found this in the /var/log/syslog:

 

Aug 12 20:55:31 raspaberri emby-server[13884]: *** Error in `/opt/emby-server/system/EmbyServer': double free or corruption (fasttop): 0x01e1aef0 ***

Aug 12 20:55:31 raspaberri rsyslogd-2007: action 'action 11' suspended, next retry is Sun Aug 12 20:57:01 2018 [v8.16.0 try http://www.rsyslog.com/e/2007 ]

Aug 12 20:55:33 raspaberri systemd[1]: emby-server.service: Main process exited, code=killed, status=6/ABRT

Aug 12 20:55:33 raspaberri systemd[1]: emby-server.service: Unit entered failed state.

Aug 12 20:55:33 raspaberri systemd[1]: emby-server.service: Failed with result 'signal'.

 

Emby is running on a raspberry pi 3 running ubuntu server 16.04. I don't see anything interesting on the emby logs themselve, although I do see a lot of these while the movie was playing:

 

2018-08-12 20:55:30.906 Info HttpServer: HTTP Response 500 to 192.168.1.183. Time: 120ms. http://192.168.1.112:8096/videos/b026942d53ca4f78c4f244b8cc641e6b/stream.mkv?DeviceProfileId=deaf0e487b9a5d7909aab631fd7e797c&DeviceId=test&MediaSourceId=b026942d53ca4f78c4f244b8cc641e6b&Static=true&AudioStreamIndex=1&Tag=a1893bd6fcf7c085df9133b2bbe76547&dlnaheaders=true 

 

It was the first movie I've tried to watch using emby. I like it very much, I hope it's something we fan figure out!

 

All help is welcome. Thanks a lot for a very cool app!

 

[Luke 42078]

Hi, can you attach the emby server log? also if you go into dlna settings on the server, what is the value of the alive message interval setting? thanks !

[mrsimo 0]

I've attached the logs from the first crash. Let me know if you need anything else there.

 

The value of "Alive message interval (seconds)" is 1800. I haven't touched this, as far as I remember.

 

The service was unresponsive this morning. I had to kill it and start it again.

 

I'll toggle the debug logging the next time I see a movie.

embyserver-63669704526.txt

Edited August 13, 2018 by mrsimo

[doonze 30]

I'm not a big fan of DLNA, not just with Emby, but in general. It's buggy at best, down right problematic at worst. This doesn't address your problem, but I do have a suggestion. I find it's at 100% better experience to just use the browser built into PS4 and and access the Emby server directly that way. You get the same interface as if you were using a computer. It's such a better experience all around in my option.

 

To me DLNA is only useful if you have NO other options. I'm sure there are exceptions, but most devices implement it poorly. 

 

If your service is stopping however, you may have other and bigger issues that need sorting. But give the browser a try! 

[mrsimo 0]

I will try the web browser! Thanks for the recommendation. I've always had a server running at home with serviio as a DLNA server, and could see my content on the TV with no problem. I've been trying to figure out if I can use a raspberry pi instead of the server, for lower power consumption, and serviio has just been a massive failure so far, so I decided to try emby. Emby doesn't work well with the TV, but the ps4 seemed to work well, so I started using that.

 

Anyhow, I checked again and the process died without playing anything. This was on the syslog:
 

Aug 13 09:03:51 raspaberri systemd[1]: emby-server.service: Main process exited, code=killed, status=11/SEGV

Aug 13 09:03:51 raspaberri systemd[1]: emby-server.service: Unit entered failed state.

Aug 13 09:03:51 raspaberri systemd[1]: emby-server.service: Failed with result 'signal'.

[doonze 30]

I'm no expert, but that looks like your server it trying to access some memory that's not assigned. 

 

You could, in fact, have found a bug. 

 

I don't think DLNA is heavily used around here, in fact it's been broken a few times (and wasn't working at all for a few versions). Using Emby just for DLNA is kinda like buying a Ferrari to get groceries. Sure, it will do it, but it's WAY overkill!

 

For years I used Kodi (xbmc back in those days) and an HTPC. I had need to change the way I viewed my media, and found Emby (called Mediabrowser back then). The power of Emby is it's interface, multi-client support, and ability to transcode your media to whatever format your client can play. But with DLNA it's just a file indexer really. All it's doing it pointing your device to the network path of the files location. 

 

PS4 has a decent implementation of DLNA really, but it's still DLNA. I think you'll be happy if you take the time to figure out using the browser. Last time I used it, about a year ago, it had an annoying quirk. I think it was something to do with media still playing in the background even if you backed out. But I don't remember exactly. More a little nuisance than a deal breaker. But it sure beat DLNA. 

 

Just point your PS4 browser to http://your-server-ip:8096 and see what you think. If you haven't used Emby this way you may have to set some stuff up. 

[doonze 30]

Sorry, I just realized your using a PI now.... they work well if you are direct-* but they don't often have the horsepower to transcode well. Some people have luck, but you'll have to google "transcoding with a PI in Emby" (or the like) for some tips. And really dig into it I'm betting. Course it's only an issue if you NEED to transcode. And that's going to depend on what kind of media you have.  

 

I love Emby, and I'm a huge supporter, but both Emby and Plex struggle on PI's. Live transcoding a high bitrate stream (like HD) is really at the edge of their ability. I can see why DLNA is attractive in your case. Your putting the work off on the client. But then your limited to codec/containers your devices can understand nativity. 

 

This may be more work than you willing to to do, but Emby has this spiffy new(ish) feature that you can convert media to a "universal" easily streamed format. You can even have it auto convert all new content. I think this may be the answer to those using the PI. In theory. But as of yet it's not very automatic. Search here for more on that as well.

[Luke 42078]

It would actually be a useful test just to turn off all dlna features, restart the server, and then see if it happens again. thanks.

[ronster76 0]

I just found the same issue with the following error:

emby-server.service: Main process exited, code=killed, status=11/SEGV

 

I'm running on a Raspberry Pi 2 - Linux serverpi2 4.14.52-v7+ #1123 SMP Wed Jun 27 17:35:49 BST 2018 armv7l GNU/Linux

This is on Raspbian (9.4), running Emby server 3.5.2.

 

I have DLNA enabled (for my PS3) and had set the blast alive message interval to 60 at one point.  It appears to have crashed when my wife's Windows box woke up and queried the network.  Specifically it seems to have crashed between the /description.xml query and the /contentdirectory/control query.

 

I'll turn off DLNA, and let you know.  I had used minidlna in the past, but prefer to use Emby as I like the additional features and prefer to manage only one service.  I also use a Kodi box and a PS4 (usually through DLNA).  All media is direct play, as the pi can't transcode well.

 

I appreciate any help with these DLNA issues. 

embyserver-63670027672.txt

Edited August 16, 2018 by ronster76

[Luke 42078]

Thanks for the info. Let us know if turning off the dlna features changes anything.

[pianoman730 0]

Is there any solution to this? I'm having the same issue on a raspberry pi 3. I get the same exact error. I've been able to use emby on it quite a bit with my roku stick, but it seems like after an hour or so after I'm not using it for a bit, it dies. I have to reinstall completely to get it to work again. 

[ronster76 0]

Emby has not crashed on me since I turned off the DLNA features. I now run a separate service (minidlna) for those clients (PS3) that don’t have another way to access Emby.

[Luke 42078]

@@ronster76 I don't think you'll see this anymore with the upcoming new release of emby server, which will be in the next couple days. Please let us know how you get on once you have that. Thanks.

[SuperCurro 4]

I think I have the same problem

 

I have test with Versión 4.1.0.26 and  4.1.1.0 with same result.

 

Now I will disconect DLNA

Jun 30 15:48:27 SERVIDOR1 EmbyServer: Not replacing existing, living, managed instance with new object.
Jun 30 15:48:28 SERVIDOR1 EmbyServer: Not replacing existing, living, managed instance with new object.
Jun 30 15:48:29 SERVIDOR1 EmbyServer: Not replacing existing, living, managed instance with new object.
Jun 30 15:56:02 SERVIDOR1 EmbyServer: message repeated 539 times: [ Not replacing existing, living, managed instance with new object.]
Jun 30 15:56:06 SERVIDOR1 EmbyServer: Not replacing existing, living, managed instance with new object.
Jun 30 15:56:11 SERVIDOR1 EmbyServer: message repeated 2 times: [ Not replacing existing, living, managed instance with new object.]
Jun 30 15:56:11 SERVIDOR1 emby-server[643]: *** Error in `/opt/emby-server/system/EmbyServer': double free or corruption (fasttop): 0x00007f46e001ef20 ***
Jun 30 15:56:11 SERVIDOR1 emby-server[643]: ======= Backtrace: =========
Jun 30 15:56:11 SERVIDOR1 emby-server[643]: /lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7f478f6a67e5]
Jun 30 15:56:11 SERVIDOR1 emby-server[643]: /lib/x86_64-linux-gnu/libc.so.6(+0x8037a)[0x7f478f6af37a]
Jun 30 15:56:11 SERVIDOR1 emby-server[643]: /lib/x86_64-linux-gnu/libc.so.6(cfree+0x4c)[0x7f478f6b353c]
Jun 30 15:56:11 SERVIDOR1 emby-server[643]: [0x7f4715956afa]
Jun 30 15:56:11 SERVIDOR1 emby-server[643]: ======= Memory map: ========
Jun 30 15:56:11 SERVIDOR1 emby-server[643]: 00400000-00419000 r-xp 00000000 fd:01 1969693                            /opt/emby-server/system/EmbyServer
Jun 30 15:56:11 SERVIDOR1 emby-server[643]: 00618000-00619000 r--p 00018000 fd:01 1969693                            /opt/emby-server/system/EmbyServer
Jun 30 15:56:11 SERVIDOR1 emby-server[643]: 00619000-0061a000 rw-p 00019000 fd:01 1969693                            /opt/emby-server/system/EmbyServer
Jun 30 15:56:11 SERVIDOR1 emby-server[643]: 00db2000-08bbc000 rw-p 00000000 00:00 0                                  [heap]
Jun 30 15:56:11 SERVIDOR1 emby-server[643]: 7f460c000000-7f460ffed000 rw-p 00000000 00:00 0
Jun 30 15:56:11 SERVIDOR1 emby-server[643]: 7f460ffed000-7f4610000000 ---p 00000000 00:00 0
Jun 30 15:56:11 SERVIDOR1 emby-server[643]: 7f4610000000-7f4613d49000 rw-p 00000000 00:00 0
Jun 30 15:56:11 SERVIDOR1 emby-server[643]: 7f4613d49000-7f4614000000 ---p 00000000 00:00 0
Jun 30 15:56:11 SERVIDOR1 emby-server[643]: 7f4614000000-7f4614021000 rw-p 00000000 00:00 0

[ronster76 0]

Just to note that since Luke posted about the updated version, the DLNA support has been working very well. Since I was able to rely on it, I paid for premiere, even though I’m not using things like transcoding. I would suggest that if you are on a raspberry pi like I am to update your system (sudo apt update && sudo apt upgrade and sudo apt dist-upgrade) to ensure the most up to date kernel and libraries at a minimum. (Update: I see you are on x86_64 architecture, so my scenario is a bit different than yours)

Edited June 30, 2019 by ronster76

[Luke 42078]

Thanks for the feedback.