shed more light on process exit 4

[ozsay]

We are packing a CLI tool using pkg and we see that on some machines, the binary exits with code 4.

I saw this https://github.com/vercel/pkg/blob/master/prelude/bootstrap.js#L1505

I'm wondering on the possible reasons why it would happen.

we are building the binary on a linux machine (for both linux and macos).

Binary works on the linux machines but fails on some macos machines.

[pojntfx]

Can reproduce this; see #1194 👍

pojntfx@bd5326fa913b:~/Projects/grpc-examples/mather.js/testing$ pkg -t host main.js 
> pkg@5.2.1
pojntfx@bd5326fa913b:~/Projects/grpc-examples/mather.js/testing$ ./main 
pojntfx@bd5326fa913b:~/Projects/grpc-examples/mather.js/testing$ echo $?
4
pojntfx@bd5326fa913b:~/Projects/grpc-examples/mather.js/testing$ export NODE_OPTIONS="--max_old_space_size=4096 --trace-exit"
pojntfx@bd5326fa913b:~/Projects/grpc-examples/mather.js/testing$ ./main 
(node:2980) WARNING: Exited the environment with code 4
    at exit (internal/process/per_thread.js:174:13)
    at _compile (pkg/prelude/bootstrap.js:1682:29)
    at Module._extensions..js (internal/modules/cjs/loader.js:1097:10)
    at Module.load (internal/modules/cjs/loader.js:933:32)
    at Module._load (internal/modules/cjs/loader.js:774:14)
    at runMain (pkg/prelude/bootstrap.js:1739:12)
    at internal/main/run_main_module.js:17:47
pojntfx@bd5326fa913b:~/Projects/grpc-examples/mather.js/testing$ export NODE_OPTIONS=--max_old_space_size=4096
pojntfx@bd5326fa913b:~/Projects/grpc-examples/mather.js/testing$ export NODE_OPTIONS=""
pojntfx@bd5326fa913b:~/Projects/grpc-examples/mather.js/testing$ ./main 
Hello, world!

[github-actions]

This issue is stale because it has been open 90 days with no activity. Remove the stale label or comment or this will be closed in 5 days. To ignore this issue entirely you can add the no-stale label

[github-actions]

This issue is now closed due to inactivity, you can of course reopen or reference this issue if you see fit.

[gclements-chwy]

I don't have an exact reason, but I can guess. You are trying to invoke a node instance with a size of max-old-space-size inside a node instance with a size of max-old-space-size and it goes boom.