I’m based in the UK so it’s getting late here today, but if you send a test build I can test what you need me to over the weekend.
As far as I can tell the increased memory usage doesn’t have any negative impact to anything I use Plex for, though I wouldn’t call myself a heavy user (one Shield as main TV and a few Android/Apple devices).
However, you mention lineup matching being in memory - that might be something, I use XMLTV and the source file I generate for that using mc2xml is large - I asked about that in another post you had responded to regarding large XMLTV files:
It feels to me like this issue is likely related.
Is there a way to see if the guide refresh could cause a similar issue - is there a way to manually run the guide refresh task? I ask this because originally I thought the guide refresh increased the memory usage but was never sure when the refresh happened to be able to test around that suspicion, but then I found this large increase which is why I created this thread.
From what I have observed, memory is not freed up later on. I haven’t stopped/restarted Plex Server since this morning from the testing I did and currently Plex Dashboard is reporting around mid-40% still, as it was after the increase in the screenshot from earlier today, seen above, and Synology task manager is reporting 3.29GB for the Plex Server process.
