AI & Agent Dev Bug Sandbox Back to Radar

Turbopack Dev: Route Handler Compilation After Pages Causes Linear Memory Blow-Up (Regression In 16.3.0-Canary.101)

Turbopack dev server consumes ~16 MB × number of previously compiled pages for each subsequent route handler compilation. Ordering matters: requesting handlers before pages avoids the blow-up. Regression introduced in 16.3.0-canary.101.

criticalConfidence 68%Next.js Affected V16.3.0-Canary.101 Affected V16.3.0 Affected V16.3.4 Affected V16.3.5

Origin Analysis

A Turbopack incremental graph bug introduced by one of the server-HMR changes (#94948, #95661, #95795, #95546) causes each route handler compilation to include all previously compiled page modules, leading to linear memory growth with page count.

1. Reproduce with provided script: node gen.mjs generates 50 pages and 34 handlers. 2. Run `node drive.mjs pages-first` (pages then handlers) -> RSS grows from 1.1 GB to ~29 GB. 3. Run `node drive.mjs handlers-first` -> RSS stays ~1.4 GB. 4. Confirm regression with bisect: 16.3.0-canary.100 good, 16.3.0-canary.101 bad.

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

Clearing the cache may increase compile latency for subsequent requests and can introduce race conditions under concurrent handler requests. This is not a root-cause fix; users should test thoroughly and rollback by removing the patch if performance degrades. Upstream fix should be preferred.