3 people reported
All time, since Sep 9.
Aborted image request hangs cache key
“What it fixes: on next start, a client that cancels a /_next/image request for a *local* image on a cold cache key can leave that key permanently pending.”
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/4183/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
Aborted image request hangs its cache key until restart. On next start, a client cancelling a /_next/image request on a cold cache key leaves later requests for that URL with no response.
Is this your bug?
File my report- Where
- Image optimizer
- Versions
- 15.5.25 to 16.4.0-canary.22
- Platforms
- macOS, Windows
- How bad
- Stops work: a core feature can't be used.
Not quite your bug?
Original reports4, newest first
- next/image: please backport #98168 to 15.5.x (cancelled image request hangs that image until restart)On GitHub#99290
- next/image: backport #98168 to 15.5.x — a cancelled request strands its /_next/image cache key under next startOn GitHub#99281
- Image optimizer: a client abort permanently wedges that /_next/image cache key for the life of the processOn GitHub#98963
- next/image: a client that disconnects mid-request permanently hangs that /_next/image cache key for every later client (self-hosted)On GitHub#98402