Version 1.13.3.5223 - Plex Server burning through memory + segfaults

Plex Media Server Desktops & Laptops
1

For context, I use the linuxserver.io PMS container instead of the official, and I use this on Ubuntu 16.04.

Since I restarted the docker container (and subsequently updated the plex version) my PMS has been absolutely thrashing through the memory on my host. I notice that when I start it, it seems to be fine. After I actually start to play something its almost as if there is a memory leak and it will go through all the memory on the host and start creating IO issues due to it using the swap. I have also noticed that its actually hitting a few segfaults as well which is pretty abnormal.

I attempted to do some googling before creating this post, and it seems that there was at least one other topic that was made here for a Server 2016 user: PMS Version 1.13.3.5223 crashing on Windows Server 2016

And another on /r/plex subreddit describing similar issues for the last few days, again just odd behavior as a whole in the same time span: https://www.reddit.com/r/PleX/comments/8w8amj/pmschromecast_performance_got_worse_over_the_last/

Is there any meaningful information I can provide to the dev team to help investigate why this may be occurring?

2

I don’t handle docker but can you reproduce it with the official container?
If you can, the docker team will want the log files and steps to reproduce ( a how-to )
If you can’t, sadly it’s on you.

I am only responding because this came into the Linux forum as well and I wanted to make sure it was properly classified for Docker.

3

I believe I figured it out. Plex was eternally looping over a particular .mkv episode which had an extremely long name to an improper Sonarr import. It had all 12 episodes in a single filename. Because of that plex didn’t like it. I was doing some other work with rClone and saw that for some reason something was continually accessing a specific folder over and over and over and over again.

With that being said I’m wondering if this would be an opportunity to add some sort of retry count so it doesn’t sit and waste resources eternally.

4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.