PMS Memory Leak on TVS-673 NAS

[rhall75]

Server Version#: Version 1.18.0.1913
Player Version#: Version 1.18.0.1913

My PMS is running on QNAP TVS-673 NAS with 8GB of RAM. There seems to be a memory leak with the PMS DLNA Server service on the QNAP TVS-673 NAS. The PMS server will eventually take up 99% of the RAM. Once I kill the PMS app on the NAS the RAM decreases to under 10%. Once I restart the PMS server the RAM will slowly start increasing again over several days until it is back to 99% RAM utilization. This has been going on for over a year now and I have done many NAS and PMS server updates over the course of a year. It is definitely DLNA causing the issue. If I disable it in PLEX the RAM utilization drops down to 13%.

[nibbles]

Thanks for the report. Can we get some debug mode Log files?

We don’t need the verbose part.

Maybe reboot the NAS first, give it 6min after it’s fully booted for PMS to initialize, then grab the logs with Settings - Troubleshooting - Download Logs. Zip up what it gives you thanks.

I just want to doublecheck a clean set of logs that there’s nothing obvious.
You’ve located what seems like a memory leak, yes.

Log Files | Plex Support

[rhall75]

Thanks Nipples. I reenabled DLNA in Plex, enabled logging, rebooted NAS and waited 6mins. Attached are the log files.

Plex Media Server Logs_2019-10-16_07-47-36.zip (6.29 MB)

[nibbles]

Hey, I spotted a leak

Oct 16, 2019 07:38:11.074 [0x7f453ca24700] ERROR - Error parsing allowedNetworks '192.168.7255.255.255.0': Invalid argument

There are invalid characters in your Settings - Show Advanced - Network
The proper IP/Mask for List of IP addresses and networks that are allowed without auth would be something like this

192.168.7.0/255.255.255.0

See also:

Authentication for local network access | Plex Support

[rhall75]

Great, thanks! I changed it in my settings. See attached.

[rhall75]

Good morning, Did you see any other issues in the logs. The RAM utilization is still increasing, because of the PLEX DLNA Service. It’s at 74% now and probably by tomorrow it will be at 99%. Do you want me to send you the logs again, now that it has been running a few days?

Thanks again for your help!

[nibbles]

I’m sorry to hear that it’s been going on for a year and keeps at it.

Let’s screenshot the memory leak, then do a clean reboot of the NAS, a 6-10min pause after PMS comes up to let it initialize, then download fresh log files. I’ll scan them for abnormal characters and other errors in general.

In your QTS Control Panel - Resources Monitor - in the lower right.
Click the header to sort by that column and then expand the arrow next to PMS.
Screenshot that

That’s how it looks on my QTS-4.3.6. Sorry if you’re on 4.4.1 and it’s different. I don’t have that yet and won’t risk it.

Have you ever run a PMS beta? We could attract more attention testing against that, but we’d also need more details about what seems to make your QNAP configuration unique.

Thank you sir

[pshanew]

Hi. I just wanted to point out that there are several threads related to DLNA leaking memory; it’s a known issue:
https://forums.plex.tv/search?q=dlna%20memory

From what I’ve read, at least one Plex employee has acknowledged this and confirmed that their engineering team is trying to track it down.

However, if you’re not using any DLNA clients (none of the Plex clients require it) you can safely disable DLNA.

[ChuckPa]

Yes, I can confirm DLNA does have a memory leak which Engineering is attempting to locate.

If DLNA isn’t needed, please disable it.

Beginning with PMS 1.18.1, by default, all new PMS installations will initialize with DLNA turned off.

[rhall75]

Thanks Nibbles, Philipsw, and ChuckPA. I’ve “google” searched for months and all I ever read was people complaining about it and saying that PLEX wasn’t doing anything about it. I am REALLY glad to see from this thread that engineering is indeed aware and trying to figure it out. I should have searched PLEX support first, instead of relaying on the almighty google.

I appreciate the info. Hope you all have a great weekend!