René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Process crashes when using `child_process.spawnSync(..., {stdio: ['pipe', 'overlapped', 'pipe']})`","articleBody":"### Version\r\n\r\nv21.7.1\r\n\r\n### Platform\r\n\r\nLinux my-laptop 6.5.0-26-generic #26-Ubuntu SMP PREEMPT_DYNAMIC Tue Mar  5 21:19:28 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux\r\n\r\n### Subsystem\r\n\r\nchild_process\r\n\r\n### What steps will reproduce the bug?\r\n\r\n```js\r\nimport {spawnSync} from 'node:child_process'\r\n\r\nspawnSync('node', ['--version'], {stdio: ['pipe', 'overlapped', 'pipe']});\r\n```\r\n\r\n```\r\n$ node example.js\r\n\r\n  #  node[6410]: int node::SyncProcessRunner::ParseStdioOption(int, v8::Local\u003cv8::Object>) at ../src/spawn_sync.cc:941\r\n  #  Assertion failed: \"Unreachable code reached\" \": \" \"invalid child stdio type\"\r\n\r\n----- Native stack trace -----\r\n\r\n 1: 0xe2fcb7 node::Assert(node::AssertionInfo const&) [node]\r\n 2: 0xf4cc3f node::SyncProcessRunner::ParseStdioOption(int, v8::Local\u003cv8::Object>) [node]\r\n 3: 0xf4d8ba node::SyncProcessRunner::ParseStdioOptions(v8::Local\u003cv8::Value>) [node]\r\n 4: 0xf4df1b node::SyncProcessRunner::ParseOptions(v8::Local\u003cv8::Value>) [node]\r\n 5: 0xf4e16b node::SyncProcessRunner::TryInitializeAndRunLoop(v8::Local\u003cv8::Value>) [node]\r\n 6: 0xf4e538 node::SyncProcessRunner::Spawn(v8::FunctionCallbackInfo\u003cv8::Value> const&) [node]\r\n 7: 0x7b7167e0eadd \r\n\r\n----- JavaScript stack trace -----\r\n\r\n1: spawnSync (node:internal/child_process:1110:29)\r\n2: spawnSync (node:child_process:876:24)\r\n3: file:///home/me/Desktop/a.js:3:1\r\n4: run (node:internal/modules/esm/module_job:222:25)\r\n\r\n\r\nAborted (core dumped)\r\n```\r\n\r\n### How often does it reproduce? Is there a required condition?\r\n\r\nI have only tried it on Linux. Since `overlapped` is intended for Windows, the behavior might differ there.\r\n\r\nThis only crashes with `spawnSync()`, not `spawn()`.\r\n\r\n### What is the expected behavior? Why is that the expected behavior?\r\n\r\nThis should either behave like `pipe`, or throw an error. I am not sure which behavior would be the best there.\r\n\r\n### What do you see instead?\r\n\r\nThe process crashes.\r\n\r\n### Additional information\r\n\r\n_No response_","author":{"url":"https://github.com/ehmicky","@type":"Person","name":"ehmicky"},"datePublished":"2024-03-29T19:36:03Z","url":"https://github.com/nodejs/node/issues/52265"}