Greetings!
We ran a quick test using your
Unfortunately this is how newer V8 builds deal with out-of-memory situations: immediate process termination. In the past V8 had graceful out-of-memory handling, but its developers sacrificed that in favor of performance. You can find more information here.
Because V8 now crashes instead of reporting out-of-memory errors,
Good luck!
We ran a quick test using your
V8RuntimeConstraints configuration. It turns out that those numbers are too tight for V8 to get off the ground, much less run any script code. It exceeds those limits during initialization and kills the process.Unfortunately this is how newer V8 builds deal with out-of-memory situations: immediate process termination. In the past V8 had graceful out-of-memory handling, but its developers sacrificed that in favor of performance. You can find more information here.
Because V8 now crashes instead of reporting out-of-memory errors,
V8RuntimeConstraints is no longer generally useful. We recommend that you avoid it unless your application uses a Chrome-like multi-process architecture that withstands process crashes.Good luck!