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
Every morning we wake up with the ability to change who we are and how we act and react.
If you’re sincere, you’ll use that to improve who you are tomorrow.
If you’re truly sorry, you’ll do something extra to help others in some way and address the karma imbalance you’ve caused. Apologise to those people you hurt. (Trust me, it will mean something to them) Find ways to help others survive bullying. Make anonymous donations to the places you stole goods from.