-
Notifications
You must be signed in to change notification settings - Fork 30.9k
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
streams: backpressure is broken in multi push cases on master #19601
Comments
/cc @nodejs/streams @mcollina |
I'm traveling this week, so I will have time to have a look next week, or this week during my flights. @addaleax it's definitely that line. However, something else is at play: |
I think that line needs a `&& !state.length`
…On Mon, Mar 26, 2018, 08:48 Matteo Collina ***@***.***> wrote:
I'm traveling this week, so I will have time to have a look next week, or
this week during my flights.
If someone beats me to fixing this earlier, please don't wait for me.
@addaleax <https://github.com/addaleax> it's definitely that line.
However, something else is at play: needReadable was always true in
there. I'll keep everybody posted.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#19601 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAW_VQK1GrJ24_N-5rVe8p05XJK1tlo2ks5tiI9GgaJpZM4S6VoO>
.
|
I think it should be |
Here is my proposed fix: #19613. |
Try out the following test case with a fast readable stream, and a slow writable one that are piped together. There seems to be a bug in master where the readable one is not backpressured properly when multiple pushes are done in the read fn.
Notice how the internal buffer just keeps growing
The text was updated successfully, but these errors were encountered: