[BUG] OOM exit status inconsistent

[howshit]

Current Behavior:

We've encountered something weird recently:

We are running a script with docker image node:12.18.3-alpine, the script is causing OOM.

if we run it in "npm run oom" (oom is the script name, and the definition of this script is node scriptFileName.js), the exit code is 0, and if we are running it in "node scriptFileName.js" directly, the exit code is 139.

Expected Behavior:

I think the expected behavior is returning exit code 137.

Steps To Reproduce:

1. create a script ==> test.js

"use strict";
const list = [];
setInterval(() => {
  const record = new MyRecord();
  list.push(record);
}, 0.000001);
function MyRecord() {
  var x = "hii";
  this.name = x.repeat(100000000);
  this.id = x.repeat(100000000);
  this.account = x.repeat(100000000);
}
setInterval(() => {
  console.log(process.memoryUsage());
}, 100);

2. create a package.json

{
  "name": "memory_test",
  "version": "1.0.0",
  "description": "",
  "main": "test.js",
  "scripts": {
    "oom": "node --throw-deprecation --max-old-space-size=1 test.js",
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "ISC"
}

3. run test.js with npm
   docker run --name oom_test -v <same folder with package.json>:/app -it node:12.18.3-alpine sh -c 'cd /app; npm run oom'
4. run test.js with node
   docker run --name oom_test -v <same folder with package.json>:/app -it node:12.18.3-alpine sh -c 'cd /app; node test.js'
5. check Exit Code
   docker inspect oom_test |grep ExitCode
   you will find the exit code from step 3 is 0, and exit code from step 4 is 139.

Environment:

• OS: Linux 4.19.76-linuxkit x86_64
• Node: 12.18.3
• npm: 6.14.6

[darcyclarke]

npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.

If your bug is preproducible on v7, please re-file this issue using our new issue template.

If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo

Closing: This is an automated message.

[henricook]

Did you ever get any satisfaction here @howshit ? I've got an OOM from npm run build returning an exit code of 0 at the moment