Server Version#: 1.40.1.8227
Since install a little more than a month ago Plex has slowly leaked memory. The latest version did not stop the leak.
I have found resizing the RAM for the LXC container will free the leaked memory without a restart or Plex. It has not run out of RAM so I do not know what will happen.
The image is from the Proxmox summary of the LXC. The only thing in the container is Plex.
An LXC can be dynamically resized. Both CPU and RAM.
I see what you mean, I should have looked at the results of free.
free -m
total used free shared buff/cache available
Mem: 3072 807 2136 0 128 2264
Swap: 0 0 0
As far as the original question is concerned that is solved. I should have known better. I will check in a week and see if this holds true, and I suspect it will. Thank you.
My next question is why is the cache growing when there is no activity? I have checked the play history and during the night with no usage more RAM is used.
Task Scheduler has a whole bunch of things that run overnight.
Are you running this on a machine with only 4 GB of RAM ?
If you’ve restricted the container to 4GB then I recommend you do what we recommend for all NAS processors – 8GB and forget about it.
Lots of things running an Proxmox, so all systems get the RAM they need. I tested Plex and I can successfully play 8 different 4k movies at the same time with 7 transcoding and that only needs about 2.5GB of RAM. My highest known real world session count is only 5.
I have plenty of experience doing performance tuning and after my testing I know what happens when it runs out of RAM starting a session. I will up it if needed.
Not checking the output of free before posting still bugs me, should not have missed that.