forked from lidge-jun/opencodex
-
Notifications
You must be signed in to change notification settings - Fork 0
[WRONG BRANCH] bound: limit Codex WS upstream frame and queued-response bytes to prevent OOM #266
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
+76
−3
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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 hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On the default non-Windows passthrough route,
src/server/responses/core.ts:2639-2695tees this body and continuously drains the inspection branch even when the client branch is stalled. Because a tee pulls whenever either branch wants data, that drain replenishesdesiredSizehere while the unread bytes accumulate without a byte limit innativeBody; a slow client combined with a rapidly emitting upstream can therefore still grow memory until OOM without triggering this check. Apply the byte budget after the tee, or route this transport through the single-reader bounded relay, and cover the production passthrough path rather than only reading the returnedResponsedirectly.Useful? React with 👍 / 👎.