Cache prerender signals leak memory

“Our installed 16.3.4 package lacks that cleanup in both distributed cache-wrapper variants.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/next-js/issues/4267/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Quiet. No reports in the last two weeks, down from 2 a week at the early-September peak. A workaround is known.

Memory leak from retained cache prerender signals with cacheComponents. Completed "use cache" prerenders stay pinned through non-aborted AbortSignal.any() composites in 16.3.x App Router apps, growing memory per request.

Is this your bug?

File my report

Where: use cache wrapper
Versions: 16.3.3 to 16.4.0-canary.25
Platforms: Linux, macOS
How bad: Some reports say it used to work.

Not quite your bug?

Aborted image request hangs cache key3 people

Original reports3, newest first

Sep 10, 202616.3.4 cache prerender signal retention: minimal reproduction, verified fix and passing canaryOn GitHub#98488
Sep 10, 2026Next.js 16.3.4: independent cache prerender signal-retention evidence and verified #97476 backportOn GitHub#98487
Aug 26, 202616.3.x leaks ~2 MiB per request with cacheComponents; renderSignal dropped from AbortSignal.any() in use-cache-wrapper between 16.3.0-canary.107 and 16.3.0On GitHub#97938