Ubuntu 18.04.2 LTS - Plex Server Crashes - Double free or corruption (!prev)

[g4m3r7ag]

Absolutely. Thank you for getting it to the right people ChuckPA.

[sa2000]

@jpurpura

also experienced a crash very similar to this this afternoon. Ubuntu 18.04.2 LXC container with 20CPU/8GB RAM and Plex version 1.15.1.791.

I got a monitoring alert (http ping) at 15:56 local time, and when I tried Plex was unreachable. However, when I checked systemctl status I saw this:
Mar 14 14:49:48 plex sh[28834]: ****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN....
Which is over an hour before the web interface went down. I also had the same double free or corruption error right before the crashed message. I restarted the server with systemctl restart at about 15:59 and everything came back fine. I have the log dump saved as well.

Thank you - We need to see more examples of logs to try and see if there is a pattern / consistency before crashing and would need the info about te double free and exactly what time it trigerred. Also if it is specific to a version of unbuntu

So make sure you run with debug logging enabled on the server
See https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/

and capture logs zip after a crash and restart and the details of the double free - exact time / message

See
https://support.plex.tv/articles/200250417-plex-media-server-log-files/

[sa2000]

@kburk1

I believe I’m seeing the same issue, but not running in a container (LXC or docker). Direct install running Ubuntu 18.04.2 LTS. I’ll be keeping an eye out on this thread if there is any progress with figuring out the cause of the crashes.

I’ve updated to the latest version of PMS ( 1.15.1.791) and haven’t seen a crash yet on that version, but I’ve only recently updated to it. Still monitoring.

Thank you - i can see that you have had a number of similar crashes from your server with 6 dumps uploaded between 28th Februrary and 13th March

The problem we have with these is that stack frames are corrupt and do not indicate where in Plex Media Server we came from before crashing in module. I will have a look at all the uploaded dumps but would like to see as many logs as possible with debug logging enabled to see if there is a a pattern - also exact time of the double free error

[kburk1]

Server Version#: 1.15.1.710

Hi,
Been experiencing server crashing once and a while over the past month. Not sure exactly when it started, but I’ve captured the most recent 2x crash files (attached). Could I get some assistance debugging these files? I’ve also attached the most recent logs shortly after the latest crash.

Please let me know if there is any additional information I should include.

Edit:
Removing logs/dump files, PM if still required.

Thanks,
Kevin

[ChuckPa]

Kevin,
There is a lot going on there and very little information to aid.
I can, at best see, 17 users including yourself, streaming at the time it was ordered to shut down.

Mar 01, 2019 20:53:00.180 [0x7f1080c73700] DEBUG - Shutting down with signal 15 (Terminated)
Mar 01, 2019 20:53:00.180 [0x7f1080c73700] DEBUG - Ordered to stop server.
Mar 01, 2019 20:53:09.568 [0x7f107a7fc700] WARN - WebSocket: Ignoring message

It didn’t crash; it was commanded.
It was responding to all the clients with exception of a WebHooks (Alexa type) device.
That device wasn’t responding.

Does this make any sense to you?

[kburk1]

Thank you for the information. Let me check into that device. Not really sure why that would have commanded it to shutdown though, but it gives me somewhere to start looking. Appreciate the help.

Thanks,
Kevin

[kburk1]

I just went back to the terminal and I do see a crash file was created though. Would that make sense if the plex server was commanded to shutdown?

Mar 01 20:43:25 p-serv-01 sh[14427]: ****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Crash Reports/1.15.1.710-ece95b3a1/PLEX MEDIA SERVER/4bdc7f2b-47e7-0980-422d4f82-045b2eaa.dmp

This crash report is attached in the original post in “Plex Media Server Crash Files.zip”

Thanks,
Kevin

[ChuckPa]

Thanks for letting me know. I unfortunately am not equipped to analyze crash dumps. Only Engineering has those files (Debug)

I will forward the Crash Report to them on Monday when in the office

[kburk1]

Sounds good. Thanks!

[kburk1]

Hi ChuckPA, just a friendly reminder. Did you get a chance to send the crash files to engineering?

[ChuckPa]

Yes. I sent them. I have nothing back from them.
We are diagnosing a problem which appears to be very closely related (perhaps same issue).
When they have an answer, I will reply.

[kburk1]

Hi ChuckPA, I was doing a bit of looking around and I noticed this other user posting a similar issue of what I’m seeing. I didnt notice it before, but I do see a “double free or corruption (!prev)” message in the plex server status when the crash report is written.

Ubuntu 18.04.2 LTS - Plex Server Crashes - Double free or corruption (!prev)

Server Version#: 1.15.1.710 Player Version#: Many/NA I keep getting crashes that state the error in the title. The service however still shows it is running. A restart fixes it for a few days but it’s annoying as service checks still report running so I don’t know it’s crashed unless I go to watch something or a user reports that it is down. I tried doing a check/repair of the database following all the steps on the Plex KB regarding that and the issue is still occurring. Googling that error…

Mar 12 17:59:04 p-serv-01 sh[16821]: double free or corruption (!prev)
Mar 12 17:59:04 p-serv-01 sh[16821]: ****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Crash Reports/1.15.1.710-ece95b3a1/PLEX MEDIA SERVER/4e893891-d665-052f-4f7b1cf2-1a178bd2.dmp

I have 3x more crash reports that have been created since the original ones I sent. If you think they would be of any use, let me know and I’ll send them your way.

Thanks,
Kevin

[ChuckPa]

Thanks. I have forwarded this to our Crash guru

[sa2000]

I am going to merge this topic with the other linked topic, I have edited the title to Ubuntu 18.04.2 LTS - Plex Server Crashes - Double free or corruption (!prev)

Ubuntu 18.04.2 LTS - Plex Server Crashes - Double free or corruption (!prev)

Server Version#: 1.15.1.710 Player Version#: Many/NA I keep getting crashes that state the error in the title. The service however still shows it is running. A restart fixes it for a few days but it’s annoying as service checks still report running so I don’t know it’s crashed unless I go to watch something or a user reports that it is down. I tried doing a check/repair of the database following all the steps on the Plex KB regarding that and the issue is still occurring. Googling that error…

[sa2000]

i have merged two topics - sorry if it makes the flow not chronological but at least we have the same problem in one place

[kburk1]

Thanks sa2000.

I just had a new crash running PMS ( 1.15.1.791). I’ll send you the logs.

Mar 15 22:29:13 p-serv-01 sh[5417]: double free or corruption (!prev)
Mar 15 22:29:13 p-serv-01 sh[5417]: ****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Crash Reports/1.15.1.791-8bec0f76c/PLEX MEDIA SERVER/211ca1d1-52ef-e675-25975b84-24472e36.dmp

[taylrjones]

I wanted to chime in that I have gotten this crash several times (double free) as well over the past few weeks and that I am running Fedora, so it doesn’t seem to be limited to Ubuntu. I will setup debug logging as well so I can attach that the next time it happens.

PMS 1.15.1.710
Kernel: 4.19.15-300.fc29.x86_64

[ChuckPa]

@g4m3r7ag

Have you customized your PMS config in any way?

Specifically, in connection with LD_LIBRARY_PATH in the .service file or your override.conf ?

[g4m3r7ag]

I have not modified either of those files I’ve only modified settings through the GUI. Specifically, what port Plex uses (32402) and then standard media settings, what agents to use etc…

I have not set an upload speed or limited remote streams, that is set to Original. (I have gigabit fiber so the bandwidth is there). Secure connections are required. Just about everything should be default I believe.

[ChuckPa]

Thanks for confirming. I didn’t think you had. One of the devs wanted to confirm.
We were confident, if it had been altered, PMS would most likely not start at all.