[bug] TCP memory leak caused by aborted client connections when streaming data with node-fetch about koa HOT 4 OPEN

What I found is that stream is being destroyed on client connection abort. However, node-fetch stream abortion doesn't destroy the socket. I could see that by checking heap dump, this reference is not being cleared out with garbage collector since the request is not aborted. Ideally this function should be called on stream destroy.

from koa.

Seems like the issue in node-fetch is outlined here node-fetch/node-fetch#1762.

To conclude this issue is reproducible only when koa and nodeFetchV2 used together

from koa.

most likely, koa's stream pipelining could use some updates as node has introduced new pipelining features that may handle the aborts better

from koa.

do you know if this happens with native fetch?

from koa.