I would not worry about virtual memory usage. Virtual memory can include memory mapped files and does not indicate actual ram usage - only the address space that the program has opened at some point. There is little point in worrying about it.
Linux
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
Others have answered why this isn't a memory leak as such and is not as big a deal as you may think.
But if you are still concerned, you can reduce it, even if doing so is a bad idea.
-
You're running it natively which means you're probably using a systemd .service file to manage jackett. Research the .system setting "RuntimeMaxSec" - that will force a restart of the service every N seconds and prevent it growing. (This is a bad idea, but if you want to boss it around, you can)
-
Run it in docker and force a max memory setting. Docker will prevent it using more than you set. You can also restrict cpu usage this way too. docker-compose example goes something like:
deploy: resources: limits: cpus: 0.5 memory: 100m
Cache commitment is not a memory leak. Hard commit is.
Think about limiting the resources it can see/use and move forward.