You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Allow for adjustment of highWaterMark on child_process.spawn().stdout #45800
Adding configurable output chunk size with support for backpressure in child_process.spawn().stdout can improve memory efficiency and allow the use of components that expect a maximum chunk size input.
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
This issue slipped through the cracks because our previous stale bot only tracked issues and couldn't catch all the issues.
Our new stale bot flagged this, and would have closed it shortly after RenderATL, but I'm just doing it a bit early so
maintainer's can focus on new code-and-learn PRs during the event.
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.
Activity
realies commentedon Aug 5, 2023
@targos, do you know if it is likely that the following merged PRs have brought this functionality closer to possible?
I can see that this feature request is still open, but I don't know if it's still needed:
fabiospampinato commentedon Aug 18, 2023
It'd be nice if this issue received some attention. It's a relatively important issue which may not be too difficult to address.
mikethecalamity commentedon Dec 19, 2025
Any updates on this? We're still experiencing it in node 22
github-actions commentedon Jul 18, 2026
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
avivkeller commentedon Aug 9, 2026
This issue slipped through the cracks because our previous stale bot only tracked issues and couldn't catch all the issues.
Our new stale bot flagged this, and would have closed it shortly after RenderATL, but I'm just doing it a bit early so
maintainer's can focus on new code-and-learn PRs during the event.
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.