Memory leak since 1.15.x on 300+ Plex Server Instances

Hi,
it’s the Plex DLNA Server process which is constantly using more RAM.

I’ve also attached the logs for you. My test (LogMemoryUse enabled) is from 2021-05-26
Plex Media Server Logs_2021-06-01_13-26-01.zip (8.6 MB)

I will have a look - i am only working 1 day a week so not sure if it is today or next Tuesday

Can you tell me why you are using DLNA server ? Is there no Plex app for your device ?

and is it just that it is using a lot of memory or is it that the memory is not being released after DLNA is no longer active ?

With windows there is a cap of 2Gb anyway for the process as it is a 32-bit application and if there was a memory leak - i would expect it to crash after reaching 2Gb and trying to allocate more memory

It’s using more and more memory and my NAS become completely unresponsible in less than one hour. Only way for me to get the RAM free again is to disable the DLNA Server.

I have a Denon AVC-X3700H and I want to directly stream my plex organized music from my android phone(s) to the device. Actually I can do this only by enabling DLNA server to make my Plex Media Server available in the Heos App. Since I cannot play my Plex playlists and there’s the DLNA server leak this is not a solution for now.
There’s already a feature request for better Integration with HEOS:

I hope that Heos support can be added in future like already done for Sonos system. This way I can build a great Heos system in my house in combination with Plex. Also I wouldn’t need the DLNA Server as a workaround.
Maybe you can give me an info if there is actually any consideration on Plex side for better HEOS support. Thanks in advance!

:+1: Garbage collection is now on point. Tested over uptime without restarts: :+1:

So memory part of my thread could be marked as solved, and several servers in one VM behave perfectly well and predictable:

On the other hand, log spam is still strong. It is ridiculous to see 14578 lines out of 14600 wasted and pretty much burning through SSDs write cycles apart from rendering log useless. I have zero clue why there are no other mentions of this, like I won an annoying bug jackpot:

I checked the actual permissions of mentioned paths and they are readable for ‘everyone’. Issue may be related to something like misuse? I get that this is a very minor bug and would not bring it up if there was a way to suppress all that spam. Unfortunately, I have no control over it.

Just to add that I also noticed a large level of RAM usage by the DLNA process on my server on a Synology NAS, version 1.23.6.4881.

The rest of Plex was using a small amount of RAM but DLNA was using ~1GB. Ive now unticked the DLNA server as I dont really have a use for it these days but it the memory leak with DLNA is very much still there. If needed I can turn it back on & gather logs if useful.

1 Like

The Plex DLNA Server issue is known about. My concern is about the Plex Media Server process itself. I do not recommend using the DLNA server unless you have to

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