<#22152 OOM killed process not reported in command...
# github-notifications
c
#22152 OOM killed process not reported in command line Issue created by damian-gn Describe the bug When running a command with
pants run
, the scheduler (background process?) is running out of memory. However, this is not reported on the terminal. In
.pants.d/workdir/pants.log
, I have the following error:
Copy code
14:55:08.33 [ERROR] The scheduler was invalidated: Exception('pantsd process 35371 was using 8208.22 MiB of memory (above the `--pantsd-max-memory-usage` limit of 8192.00 MiB).')
But in Terminal, this is not visible:
Copy code
$ pants run :migrate
14:57:37.85 [INFO] Initializing scheduler...
14:57:37.86 [INFO] Initializing Nailgun pool for 28 processes...
14:57:38.93 [INFO] Scheduler initialized.
[ … output of my command … ]
There is no indiciation of the error, other than the fact that re-running this command forces a full venv rebuild due to the OOM kill. Pants version 2.24.2 OS macOS Sequoia Additional info Discussed in Slack: https://pantsbuild.slack.com/archives/C046T6T9U/p1743425305577379 pantsbuild/pants