Excessive Memory Usage; Plex Server 1.18.1.1973

Plex Media Server NAS & Devices
1

Same Problem on Synology NAS, here’s my info;

Server Version#: DS1019+
Player Version#: 1.18.1.1973
DSM Version: 6.2.2-24922 Update 3

I Have checked everything in my Plex settings but as soon as Plex “scans library files” or I “optimize database” the RAM usage will jump to 80+%(~4.7GB of memory) and will stay there. Or if Plex is left running on it’s own, within 24 hours the memory usage will creep back over 80%.

I wanted to try the “free -m” as suggested in another post, however; I could not see how to execute a command line instruction in DSM or Plex. I will search again for a terminal window. (SSH didn’t work for me, Telnet?)

I’ve seen this problem discussed in earlier posts, without resolution (well it was suggested the NAS’s were old, not supported, needed a DSM update or add more memory.) Since this is a newer Synology NAS, I don’t believe my problem is resolved.

Sorry for re-hashing an old topic, I’ve not seen a remedy/fix. If my Google-fu was weak with one please forgive me and point me in the right direction.

Thanks in advance for any help and of course your time,

Scott…

2

using SSH on Synology only lets you sign in as user admin (their security mechanism).

  1. Terminal & SNMP
  2. Enable SSH
  3. Assign a password to admin that you know.

Do you have DLNA enabled? If so, and you don’t need it, turn it off; it leaks.

3

I can login using putty, user ID, then PW, no problem. Unfortunately, there’s no free -m command. I login, issue the basic sudo su, look at all available commands, no “free” command. Logging in with win 10 through CMD=>SSH, is even less helpful.

Please let me know where I’m going wrong. I think it’s something basic, who knows…

I will try turning off DLNA, see what that does. Thanks for the tip.

4

moesern is my Synology DS1815+

[chuck@lizum ~.165]$ gom
admin@moesern's password: 
admin@moesern:~$ free -m
              total        used        free      shared  buff/cache   available
Mem:           7973         343        7169          37         461        7337
Swap:          2047           0        2047
admin@moesern:~$ uname -a
Linux moesern 3.10.105 #24922 SMP Wed Jul 3 16:37:24 CST 2019 x86_64 GNU/Linux synology_avoton_1815+
admin@moesern:~$
5

Did you SSH via Linux? I can try that, I have a Ubuntu laptop that I can use. Probably should of used it to begin with.

Thanks for your reply, Scott.

6

Yes, I did use ssh. It’s the only way to gain shell level access to a Synology.

7

Using Ubuntu to SSH into Synology, the Free -m worked, kinda, well the command worked as described. It did reduce memory usage from 87% to 65%. If I close the Plex Media Server package through the Package Center, memory usage drops to 12 percent.

If anyone knows what’s up, has another idea…anything, I’ll certainly give it a try.

8
  1. free -m is an inspection tool. It does nothing to actually free up memory.
  2. I suspect the primary cause is the DLNA server if not already disabled. It is enabled by default.
9

If I disable the Plex Media Servers DLNA option, will my Plex media players still locate the 1019+ as our Plex Media Server? I was under the impression that any local players required a “DLNA Server”. That sounds a little confused, but do you get what I am trying to say?

10

If you are accessing them with Plex apps - then you don’t need the DLNA server.

If you are using the DLNA client app in your television and devices, then yes you will.

11

Yes, exactly as you thought. I disabled the DLNA server in PLEX, Settings>Server>DLNA and memory usage immediately dropped from 72% to 19%.

Is this a known issue or expected behavior in all DLNA Media servers or just Plex? I really like Plex, however; I have two older TV 's that do not have native Plex support. Suppose, I can buy a couple of cheap (used) Fire TV or ROKU USB sticks.

Hopefully they’ll resolve the issue, I do like my Plex…

12

There is a known memory leak in the DLNA server.
DLNA is turned off by default unless previously manually turned on until Engineering finds the source of the memory leak.

13

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