fix: Writing to Bun.stderr causes CPU pinning to 100%. #5396
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.
Seen on macOS Sequoia 15.7.2 . Probably bug in Bun. writing directly to process.stderr works around it. Tested with Bun 1.3.4.
The bug is only seen when process stderr is piped to another process such as tee like
bun run dev -- serve --port 0 --print-logs --log-level INFO 2>&1 | tee -a test.log
And then sending api request to trigger error logs