The problem gets worse in pipelines. When you chain multiple transforms — say, parse, transform, then serialize — each TransformStream has its own internal readable and writable buffers. If implementers follow the spec strictly, data cascades through these buffers in a push-oriented fashion: the source pushes to transform A, which pushes to transform B, which pushes to transform C, each accumulating data in intermediate buffers before the final consumer has even started pulling. With three transforms, you can have six internal buffers filling up simultaneously.
// 易错点4：错误弹出栈顶 → 破坏独立车队的时间记录，导致结果错误
，更多细节参见搜狗输入法2026
ВсеСледствие и судКриминалПолиция и спецслужбыПреступная Россия
15. Survivor 50: In the Hands of the Fans
Forgetting releaseLock() permanently breaks the stream. The locked property tells you that a stream is locked, but not why, by whom, or whether the lock is even still usable. Piping internally acquires locks, making streams unusable during pipe operations in ways that aren't obvious.