I’ll test the development build if you package it in a deb for Ubuntu x86_64.
Thanks!
I have made the following development builds available to a number of you to see if the changes for a double free crash fix this one
plexmediaserver-1.15.5.934-21b6f581b.x86_64.rpm
plexmediaserver_1.15.5.934-21b6f581b_amd64.deb
1 Like
Im also getting the same error. Getting tons of sql3 busy DB’s running a large library on ssd while this is happening. Not sure if related.
I have also been getting the same crash with the same DB timeouts happening. I disabled the Relay Service and Plex is at least not crashing anymore. The server can still have streaming issues once the DB timeouts happen. I generally then need to restart the Plex service. (Debian Jessie is the server’s OS.) I have had to repair a corrupted database after it happened (https://support.plex.tv/articles/201100678-repair-a-corrupt-database/).
Just had a crash on the dev build (1.15.5.934), but no system core dump was created. Let me know if you’d like me to provide the logs.
Apr 16 18:43:17 p-serv-01 sh[1548]: double free or corruption (!prev)
Apr 16 18:43:17 p-serv-01 sh[1548]: ****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Crash Reports/1.15.5.934-21b6f581b/PLEX MEDIA SERVER/18bdb74e-a1a8-fb06-0842a46c-796cf572.dmp
@sa2000 I apologize if this has been answered.
Does engineering have the information they need to resolve this issue?
If not, could you provided an exact list of steps that engineering needs to capture the data.
I have the dev build and can reproduce the issue rather quickly. I can provide data if it is missing.
What steps are you using to reproduce the issue?
They have been trying to reproduce the crash in a debug environment but failed to get it to happen. So would welcome any information on the steps / devices needed to get it to crash.
I saw mention of needing a core dump.
In detail, how would those be captured?
For example, in my case just the plex process crashes on the box and creates a back trace. Should I add something to systemd to produce a core dump?
The only information I have the web page i linked to here Ubuntu 18.04.2 LTS - Plex Server Crashes - Double free or corruption (!prev) - #63 by sa2000
These crashes arise after memory gets corrupted
Here to add my $.02 as getting the same thing on a Fedora 29 with Plex 1.15.4.919.
Apr 21 01:00:03 stream01 sh[11628]: GUI: Requesting metadata for 'Traffic'
Apr 21 01:08:03 stream01 sh[11628]: GUI: Requesting metadata for 'American Gods'
Apr 21 01:25:43 stream01 sh[11628]: double free or corruption (!prev)
Apr 21 01:25:44 stream01 sh[11628]: ****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Crash Reports/1.15.4.919-8e2884e4b/PLEX MEDIA SERVER/28f193e2-####-369774e4.dmp
@Samwiseg0 I was able to provide an old coredump by looking through coredumpctl (check out its manpage and tutorials online).
I’m still waiting for my next crash to occur on the development build. My current theory is it may be related to available system memory, I upgraded from 32 GB to 64 GB RAM and haven’t been seeing the crash anymore for the past 8 days. Also noteworthy is there’s 32 GB of swap which was being used more often when the server had 32 GB physical RAM.
are you running anything else on the server? I just run Plex and with 8GB of memory it never touches swap. Using swap with 32GB seems like a lot
I am getting this on Ubuntu 18.04.2 LTS. I run on VMWare and this VM is dedicated to just Plex.
Apr 23 08:58:54 plexserver sh[1965]: Connection to xxx.xxx.xxx.xxx closed by remote host.
Apr 23 10:27:15 plexserver sh[1965]: Connection to xxx.xxx.xxx.xxx closed by remote host.
Apr 23 10:37:41 plexserver sh[1965]: Connection to xxx.xxx.xxx.xxx closed by remote host.
Apr 23 10:45:26 plexserver sh[1965]: Connection to xxx.xxx.xxx.xxx closed by remote host.
Apr 23 11:46:32 plexserver sh[1965]: Connection to xxx.xxx.xxx.xxx closed by remote host.
Apr 23 13:14:57 plexserver sh[1965]: Connection to xxx.xxx.xxx.xxx closed by remote host.
Apr 23 13:30:29 plexserver sh[1965]: Connection to xxx.xxx.xxx.xxx closed by remote host.
Apr 23 15:18:11 plexserver sh[1965]: Connection to xxx.xxx.xxx.xxx closed by remote host.
Apr 23 16:25:27 plexserver sh[1965]: double free or corruption (!prev)
Apr 23 16:25:28 plexserver sh[1965]: ****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Crash Reports/1.15.3.876-ad6e39743/PLEX MEDIA SERVER/7319e5fb-2b59-411f-04f52709-7e653e6c.dmp
The VM has 64GB of memory and 12 CPU cores, this does not appear to be caused by system load. However it does appear to happen while someone is watching something and the transcoder is active. I can provide the dumps and logs if it helps beyond what’s already been posted here, just let me know.
This is really killing my install. I am going to try to downgrade to 1.14.x if possible for the time being.
Unfortunately I have no logs yet as I’ve only started noticing this recently but I’ve been experiencing the same issue for around a month.
Posting my specs in case this is helpful to anyone.
PMS is running on an Ubuntu 18.04.2 LTS VM under Proxmox on a Dell R710 (32GB DDR3 ECC, 2x Xeon X5650).
VM Configuration:
RAM: 8GB (ballooning device checkbox checked, min and max set to 8192)
CPU: 2 sockets, 8 cores each, type: kvm64, NUMA enabled
HDD: 120GB Thin Provisioned, caching set to default in Proxmox (no cache)
I’ve turned on debug logging so can post logs next time the crash happens.
Had another crash tonight on the dev build. Sent my logs to the staff just now. Had an uptime of 1 week 3 days this time.
@jpurpura Yes, it’s a server that does a lot of things, Plex is one of them. I’m not a FreeNAS simpleton user.
I suffering from the same issue on Ubuntu 18.04.2 LTS and Plex 1.15.3.876 (I have updated Plex now, but it was running on 1.15.3.876 when it last crashed)
I have yet to investigate this issue more (on my end), therefore have no logs to show or a way to replicate this crash.
I will post more information if/when it crashes again.
Just wanted to raise more attention to this issue.
Another crash. Can’t find anything interesting in logs except for this useful message:
Apr 28, 2019 16:40:14.784 [0x7f1dd97fa700] WARN - Transcode runner appears to have died
Therefore unable to reproduce crash.
The crash uploader has reported this Plex devs:
Apr 28, 2019 16:53:06.208 INFO - Successfully reported 7973396b-61e8-f9ce-6763c444-60ee00fe
Ubuntu 18.04.2 LTS, Plex Version 1.15.4.993
Additional information available upon request.
Full logs zip please and indication if this is double free crash (shows in systemctl status) or not
I have sent you the logs in a private message.
Yes, this is the double free crash.
Apr 28 16:40:34 sh[10214]: double free or corruption (!prev)
Apr 28 16:40:35 sh[10214]: ****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Crash Reports/1.15.4.993-bb4a2cb6c/PLEX MEDIA SERVER/7973396b-61e8-f9ce-6763c444-60ee00fe.dmp
There were about 10 users currently watching content, when the latest crash occurred.
Ubuntu 18.04.2 LTS, Plex Version 1.15.4.993
Please let me know if you need more information.
