Avoid file descriptor 3 for IPC on Linux to prevent Chromium collision #283
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Chromium/Electron on Linux assumes file descriptor 3 is its lowest reserved control pipe in several places (e.g., Crashpad handler plumbing) and, when used, DevTools’
--remote-debugging-pipe
also binds file descriptors 3/4. If FD 3 is already a Node IPC pipe, the Chromium side can’t set up what it expects, and DevTools misbehaves. By inserting anignore
entry at index 3, we keep FD free for Chromium and put Node’s IPC on FD 4. The IPC-based feature from PR #260 continues to work normally viachild.send/process.on('message')
.Fixes #264
Closes #280
CC @caoxiemeihao