We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When the process is killed by the heap limiter, the exit code is incorrectly shown as 0.
Create a test.js file:
test.js
const numbers = []; for (let i = 0; i < 100000000; i++) { numbers.push(i); if (i % 10000 === 0) console.log(i); }
Execute the following command to trigger the heap limiter:
pm2 start test.js --no-autorestart --no-daemon --node-args="--max-old-space-size=10"
The process should exit with SIGABRT signal and a non-zero code (usually 134).
The process exits with SIGABRT signal and 0 code. This makes it impossible to determine whether the process exited normally or with an error:
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When the process is killed by the heap limiter, the exit code is incorrectly shown as 0.
Steps to reproduce
Create a
test.js
file:Execute the following command to trigger the heap limiter:
pm2 start test.js --no-autorestart --no-daemon --node-args="--max-old-space-size=10"
Expected behaviour
The process should exit with SIGABRT signal and a non-zero code (usually 134).
Actual behaviour
The process exits with SIGABRT signal and 0 code. This makes it impossible to determine whether the process exited normally or with an error:
The text was updated successfully, but these errors were encountered: