Seen recently a "RAM LIMIT EXCEEDED" or "RAM WARNING" message? your services are completely fine.

This is a display bug, not an actual problem.
Github issue completed, pending review: RAM gauge shows page cache as used memory — false warnings · Issue #331 · MagnaCapax/PMSS

 

What's really happening: The RAM gauge on the welcome page incorrectly counts Linux file cache (also called page cache) as "used memory." File cache is temporary storage the operating system uses to speed up repeated disk access — especially helpful for torrenting and other I/O-heavy tasks.

This cache is not real memory usage by your processes. The OS automatically drops it the instant any application actually needs the memory. Your real process memory usage is well within safe limits.

 

Why it looks alarming: The gauge often shows one giant red bar at 95%+ usage and displays a scary warning about processes being killed (OOM killer). That warning is misleading here. In reality, the kernel reclaims file cache long before it would ever invoke the OOM killer.

Your torrents, web panel, Plex/Jellyfin, ruTorrent/qBittorrent, and all other services continue running normally.

 

What we're doing about it: We've already developed and submitted a fix that will:

  • Separate the display into actual process memory (real usage) and file cache
  • Show them in different colors/bars for clarity
  • Trigger warnings only when real process memory approaches the limit

Once this update rolls out (should be soon), the false alarms will disappear and you'll get an accurate view of your actual resource usage.
Only pending review anymore: RAM gauge shows page cache as used memory — false warnings · Issue #331 · MagnaCapax/PMSS

 

What you need to do: Nothing at all — this is entirely on our end.

 

If you opened a support ticket about this — thank you! Your reports helped us confirm the widespread pattern and prioritize the fix.



Saturday, March 21, 2026

« Back