Skip to content

Commit

Permalink
stream: avoid pause with unpipe in buffered write
Browse files Browse the repository at this point in the history
If a pipe is cleaned up (due to unpipe) during a write that
returned false, the source stream can get stuck in a paused state.

Fixes: #2323
PR-URL: #2325
Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
  • Loading branch information
mscdex committed Oct 11, 2015
1 parent 8e21309 commit 6899094
Show file tree
Hide file tree
Showing 2 changed files with 51 additions and 3 deletions.
16 changes: 13 additions & 3 deletions lib/_stream_readable.js
Original file line number Diff line number Diff line change
Expand Up @@ -497,6 +497,7 @@ Readable.prototype.pipe = function(dest, pipeOpts) {
var ondrain = pipeOnDrain(src);
dest.on('drain', ondrain);

var cleanedUp = false;
function cleanup() {
debug('cleanup');
// cleanup event handlers once the pipe is broken
Expand All @@ -509,6 +510,8 @@ Readable.prototype.pipe = function(dest, pipeOpts) {
src.removeListener('end', cleanup);
src.removeListener('data', ondata);

cleanedUp = true;

// if the reader is waiting for a drain event from this
// specific writer, then it would cause it to never start
// flowing again.
Expand All @@ -524,9 +527,16 @@ Readable.prototype.pipe = function(dest, pipeOpts) {
debug('ondata');
var ret = dest.write(chunk);
if (false === ret) {
debug('false write response, pause',
src._readableState.awaitDrain);
src._readableState.awaitDrain++;
// If the user unpiped during `dest.write()`, it is possible
// to get stuck in a permanently paused state if that write
// also returned false.
if (state.pipesCount === 1 &&
state.pipes[0] === dest &&
src.listenerCount('data') === 1 &&
!cleanedUp) {

This comment has been minimized.

Copy link
@addaleax

addaleax Mar 29, 2016

Member

@mscdex Hope you don’t mind my asking, but are you sure this path can actually be taken? Since 2ff499c, pipesCount === 1 seems to imply that state.pipes is not an array, so state.pipes === dest would have been correct here?

debug('false write response, pause', src._readableState.awaitDrain);
src._readableState.awaitDrain++;
}
src.pause();
}
}
Expand Down
38 changes: 38 additions & 0 deletions test/parallel/test-stream-pipe-cleanup-pause.js
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
'use strict';
const common = require('../common');
const assert = require('assert');
const stream = require('stream');

const reader = new stream.Readable();
const writer1 = new stream.Writable();
const writer2 = new stream.Writable();

// 560000 is chosen here because it is larger than the (default) highWaterMark
// and will cause `.write()` to return false
// See: https://github.com/nodejs/node/issues/2323
const buffer = new Buffer(560000);

reader._read = function(n) {};

writer1._write = common.mustCall(function(chunk, encoding, cb) {
this.emit('chunk-received');
cb();
}, 1);
writer1.once('chunk-received', function() {
reader.unpipe(writer1);
reader.pipe(writer2);
reader.push(buffer);
setImmediate(function() {
reader.push(buffer);
setImmediate(function() {
reader.push(buffer);
});
});
});

writer2._write = common.mustCall(function(chunk, encoding, cb) {
cb();
}, 3);

reader.pipe(writer1);
reader.push(buffer);

2 comments on commit 6899094

@DasithKuruppu
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When is this going to be released on the binary versions ? Its been like 2 months and still the problem exists

@mscdex
Copy link
Contributor Author

@mscdex mscdex commented on 6899094 Dec 31, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@DasithKuruppu This commit has been in node releases since v5.0.0 (and not v4.x since it's a behavioral change).

Please sign in to comment.