Node.js: Memory Safety Sweep Ahead of the Jod LTS Cutoff

A version 22.24.0 LTS proposal landed alongside a cluster of use-after-free and race-condition fixes across HTTP/2, QUIC, SQLite, and the virtual file system, underscoring a broader push for reliability as the codebase heads toward release.

Duration: PT2M33S

Episode overview

This episode is a short developer briefing from Node.js.

It explains recent repository work in plain language.

  • Show: Node.js
  • Published: 2026-07-17T13:05:08Z
  • Audio duration: PT2M33S

Transcript excerpt

This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.

This is Node.js, your development briefing for July 17th, 2026.

The headline today is stability. Juan Arbol opened the proposal for version 22.24.0, "Jod," an LTS release pulling together dozens of fixes, and much of the surrounding activity reads like a pre-release hardening pass.

The clearest theme: use-after-free and race-condition bugs, fixed in parallel across several subsystems. In HTTP/2, PR 64166 fixes a heap use-after-free where a stream could close while nghttp2 was still processing incoming data — a crash bug now resolved by marking sessions as busy during receive. In SQLite, PR…

The second theme is crypto and native binding cleanup. Panva has three PRs — 64547, 64552, and 64553 — all trimming redundant memory copies and reallocations in the OpenSSL and KEM code paths, plus correcting behavior that shifted unintentionally during an earlier backend split. These are performance and correctness…

A smaller but related cluster: the virtual file system's real provider had a broken watch-file listener, flagged in issue 64536 and fixed independently in both PR 64537 and PR 64542 — a sign two contributors converged on the same known gap.

On the feature side, QUIC keeps gaining…

Nearby episodes from Node.js

  1. Streams Get a Correctness and Speed Pass
  2. HTTP Response Handling Gets a Do-Over
  3. Chasing Down Memory Leaks Across the Stack
  4. Streams and Sockets Get a Performance Pass
  5. Weekly Recap - Streams Get Faster, Threads Get Closer
  6. Streams Get Faster, Maps Get Fixed
  7. Streams Get Faster and Safer
  8. Native Fast Paths and Filesystem Hardening