Sometime over the last week or so, when I click over to the dashboard to see the currently active streams, the memory usage for the Chrome tab jumps to between 1.5GB and 2.2GB, and it slows down the entire Plex Web tab. The tab will eventually crash or I have to go into Task Manager and kill the tab before loading back up the Plex web app.
Other web functions seem to not be working very well, either. For instance, the streams indicator on the top-right will not update unless I fully refresh the Chrome tab, when clicking on Check for Updates in the settings menu, the button will stay at “Checking for Updates…” and never return any results.
I can’t recreate it here in Chrome 71 on Windows.
Memory consumption for Chrome with just the plex app open on the Dashboard view is fluctuating between 380 to 395 MB but doesn’t go up.
Is your server local or remote?
Are you using a custom domain name and/or custom cryptographic certificate to access your server?
Do you have certain domains/IP ranges blocked at the router/network level?
It is a local server with no custom certificates or domains. Nothing is being blocked at the server level, either. The graph that causes problems appears to be the bandwidth graph. I restarted the server box after all users finished their streams, and it appears to have gone away.
I use firefox and I use 4-6GB RAM(taken from the task manager)… I always just blame my 30+ tabs opened.
Well, I kill the process within Task Manager at lease once a week.
Heck I’m at 1GB with just 6 tabs open!! I’m gonna run a test and see if it IS PlexWeb.
@NewPlaza I have a lot of tabs open on my main computer as well. The 1.5 to 2.2GB was only accounting for the Plex tab (since Chrome runs each tab in a separate Windows process).
@OttoKerner, the server restart helped with the Dashboard not taking up as much memory, but widgets in the UI are still not updating properly. I ran Optimize Database, and the circle at the top just ran in circles for hours. I had to refresh the tab to have it go away. Other library updates that were done were not being properly removed from the UI, either.
