<#18630 Add a configurable timeout to pantsd after...
# github-notifications
c
#18630 Add a configurable timeout to pantsd after some amount of no-usage Issue created by sureshjoshi While trying to figure out why I seemingly had less memory available than I should (given that most of the applications on my computer were closed), I saw this as my top memory usage:

Screenshot 2023-03-31 at 7 03 16 AM

This is strange since I hadn't used or run a Pants command in these repos in over a week or two, so imagine my surprise that 7 of my top 9 processes were Pants-related. Each of them (the Pants and Python) appeared to be averaging 1.5-2% CPU as well. I'm sure that memory is all recoverable as needed, but I think having those processes stay live while doing nothing (for weeks) is a bit overkill. What is surprising is that I run processes that routinely take up all available memory for short time periods, so I thought that would inevitably cause
pantsd
to shut down due to memory pressure. pantsbuild/pants