AI & Agent Dev Bug Sandbox Back to Radar

Segment Prefetch Of An ISR NotFound() Page Never Completes In Chromium When A Service Worker Mediates Fetches (Wedges Connections, Networkidle Never Reached)

Next.js segment cache abandons response bodies for rejected prefetch responses; with a service worker, unconsumed respondWith bodies cause Chromium to keep fetches pending forever, exhausting connections and breaking networkidle.

highConfidence 92%Next.js Affected V16.2.12 Affected V16.3.1-Canary.4

Origin Analysis

When a segment prefetch response is rejected (e.g. 404 from ISR notFound), the client code does not read or cancel the response body. With a service worker using respondWith, the unconsumed body keeps the request in flight indefinitely.

1. npm install && npx playwright install chromium 2. npm run build (fresh production build) and npm start 3. node probe.mjs — exits 1 when reproduced (deterministically on fresh build) Or by hand: open Chrome DevTools → Network on http://localhost:3000/, reload once (so the service worker controls the page), and watch the segment prefetches of the dead link stay pending forever.

Fixing Code Block

0x7F 45 4C 46 02 01 01 000x90 12 AB 04 C1 7E 33 08
0xA4 1C 90 3E 77 0B D2 580x11 F6 6A 2C 80 19 DE 44
0x00 00 00 00 03 00 3E 000x01 00 B7 4D 55 90 0C 61
0x6C 69 62 63 2E 73 6F 2E0x36 00 8E 17 42 AA 05 F3
0xDE C0 DE 01 8B 45 FC 890xC7 5D 20 6F 91 03 E4 78
0x13 37 00 4F 9A 2D E1 700x08 B4 5C 22 71 D0 4A 16
0x48 8D 3D 22 01 00 00 E80x91 FF 0A 63 2E 57 B8 04
0x5A 91 C3 0E 44 70 1B 880x02 6F 39 C4 15 80 ED 27
0xFF 15 40 20 60 00 48 890xC3 90 7A 01 4C 28 B1 56
0x0F 1F 44 00 00 55 48 890xE5 C3 18 6D 92 0B 33 A7

Edge Case Audit

Cancelling a body that is already being consumed elsewhere may throw; the try/catch prevents crashes. Ensure cancellation only after confirming response is not needed. This fix is safe for both service worker and non-SW environments but should be tested with streaming/prefetch scenarios. Rollback by removing cancellation lines; no migration needed.