I have recently noticed that the Plex DLNA service seems to be regularly hogging more than 50% of my available memory (>4gb out of 8gb total). Restarting the server application temporarily resolves the issue, but memory usage creeps back up over the course of 3-4 days even if no one is using the DLNA service.
I’ve been running PMS with the DLNA service enabled on my Ubuntu Server (currently 20.04) for close to two years now, and this issue has only cropped up in the last month or so after the last couple of PMS updates.
I see several historical posts about this issue, but nothing in the last few months. I had the DLNA service disabled for a few day, but I’ve recently found a good use case for it and would really like to keep it on. I’m not really sure where to start troubleshooting this. I’ve tried monitoring the PMS console, but there doesn’t seem to be much going on related to the DLNA service.
Not strictly necessary, but definitely helpful. I’ve started using Mopidy in my ongoing quest to offset my laptop’s middling battery life with minimal command line software, and since mopidy-plex appears long dead, the DLNA server seemed like the best way to stream my Plex library through Mopidy, if only when I’m at home.
I wanted to mention, I have determined the culprit that is causing this issue to manifest on my system. We recently added a new LG Smart TV to our network, and that device seems to be constantly pinging the DLNA server at a rate of 0.5 - 2.5Kbps all the time.
This wouldn’t be causing the memory leak, but I suspect that it is the exacerbating factor has caused this issue to manifest for me recently when I had never encountered it before.
