-
Notifications
You must be signed in to change notification settings - Fork 29.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
child_process: use non-infinite maxBuffer defaults
Set the default maxBuffer size to 204,800 bytes for execSync, execFileSync, and spawnSync. APIs that return the child output as a string should have non-infinite defaults for maxBuffer sizes to avoid out-of-memory error conditions. A non-infinite default used to be the documented behaviour for all relevant APIs, but the implemented behaviour for execSync, execFileSync and spawnSync was to have no maxBuffer limits. PR-URL: #23027 Refs: #22894 Reviewed-By: Sam Roberts <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
- Loading branch information
1 parent
1656cd2
commit eb8a51a
Showing
9 changed files
with
138 additions
and
16 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
50 changes: 50 additions & 0 deletions
50
test/parallel/test-child-process-execfilesync-maxBuffer.js
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,50 @@ | ||
'use strict'; | ||
require('../common'); | ||
|
||
// This test checks that the maxBuffer option for child_process.spawnFileSync() | ||
// works as expected. | ||
|
||
const assert = require('assert'); | ||
const { execFileSync } = require('child_process'); | ||
const msgOut = 'this is stdout'; | ||
const msgOutBuf = Buffer.from(`${msgOut}\n`); | ||
|
||
const args = [ | ||
'-e', | ||
`console.log("${msgOut}");` | ||
]; | ||
|
||
// Verify that an error is returned if maxBuffer is surpassed. | ||
{ | ||
assert.throws(() => { | ||
execFileSync(process.execPath, args, { maxBuffer: 1 }); | ||
}, (e) => { | ||
assert.ok(e, 'maxBuffer should error'); | ||
assert.strictEqual(e.errno, 'ENOBUFS'); | ||
// We can have buffers larger than maxBuffer because underneath we alloc 64k | ||
// that matches our read sizes. | ||
assert.deepStrictEqual(e.stdout, msgOutBuf); | ||
return true; | ||
}); | ||
} | ||
|
||
// Verify that a maxBuffer size of Infinity works. | ||
{ | ||
const ret = execFileSync(process.execPath, args, { maxBuffer: Infinity }); | ||
|
||
assert.deepStrictEqual(ret, msgOutBuf); | ||
} | ||
|
||
// Default maxBuffer size is 200 * 1024. | ||
{ | ||
assert.throws(() => { | ||
execFileSync( | ||
process.execPath, | ||
['-e', "console.log('a'.repeat(200 * 1024))"] | ||
); | ||
}, (e) => { | ||
assert.ok(e, 'maxBuffer should error'); | ||
assert.strictEqual(e.errno, 'ENOBUFS'); | ||
return true; | ||
}); | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters