--max-executable-size not recognized after upgrade 7.10.0 => 8.0.0

[abenhamdine]

• Version:8.0.0
• Platform:Windows 10 64bits
• Subsystem: child process

The following code doesn't crash with node 7.10.0 but crashes with node 8.0.0 :

            const env = _.cloneDeep(process.env);

            const options = {
                execArgv: process.execArgv.concat(['--expose-gc', '--max-executable-size=384', '--max-old-space-size=512', '--max-semi-space-size=2']),
                env: env
            };

            const cp = child_process.fork(myPathProcess, [someArg1, someArg2], options);

The error :

C:\Program Files\nodejs\node.exe: bad option: --max-executable-size=384

DEBUG 19:38:55 : Calculation.onChildExit() : child process 7016 exited with code 9

I've suspected #12348 but failed to see how it can be related.

Have the V8 options changed ? I didn't find anything in the changelog about this.
Or is --max-executable-size the correct syntax ?

[targos]

This flag was removed in #13217 (commit).

[silverwind]

The new option for that should be --max_old_space_size.

[abenhamdine]

Ah thx a lot for the quick and precise answer !
Shouldn't it be in the changelog for 8.0.0 ?
Seems pretty common case to use this flag.

[bnoordhuis]

V8 flags come and go, we don't normally call them out in the release notes. I'll go ahead and close this.