node/lib/internal/webstreams
James M Snell 4d3923aaba
stream: fix cloned webstreams not being unref'd
When cloning a `ReadableStream` and `WritableStream`, both use an
internal `MessageChannel` to communicate with the original stream.
Those, however, previously were not unref'd which would lead to the
process not exiting if the stream was not fully consumed.

Fixes: https://github.com/nodejs/node/issues/44985
PR-URL: https://github.com/nodejs/node/pull/51255
Reviewed-By: Matthew Aitken <maitken033380023@gmail.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Debadree Chatterjee <debadree333@gmail.com>
2023-12-24 16:42:10 +00:00
..
adapters.js stream: yield expected Error class on zlib errors 2023-11-19 07:36:30 +00:00
compression.js stream: add Symbol.toStringTag to Compression Streams 2023-11-19 07:36:30 +00:00
encoding.js stream: use private properties for encoding 2023-04-13 15:22:48 +00:00
queuingstrategies.js doc: use same name in the doc as in the code 2023-08-19 16:15:22 +00:00
readablestream.js stream: fix cloned webstreams not being unref'd 2023-12-24 16:42:10 +00:00
transfer.js stream: fix cloned webstreams not being unref'd 2023-12-24 16:42:10 +00:00
transformstream.js stream: implement TransformStream cleanup using "transformer.cancel" 2023-12-15 07:54:19 +00:00
util.js stream: implement ReadableStream.from 2023-07-18 09:50:22 +00:00
writablestream.js stream: fix cloned webstreams not being unref'd 2023-12-24 16:42:10 +00:00