Skip to content

Avoid using unclosing prefetch streams in the browser#89610

Merged
unstubbable merged 1 commit intocanaryfrom
hl/unclosed-streams-leak
Feb 9, 2026
Merged

Avoid using unclosing prefetch streams in the browser#89610
unstubbable merged 1 commit intocanaryfrom
hl/unclosed-streams-leak

Conversation

@unstubbable
Copy link
Copy Markdown
Contributor

@unstubbable unstubbable commented Feb 6, 2026

Previously, createPrefetchResponseStream intentionally never called controller.close() on the wrapper stream, to prevent React Flight from erroring on unresolved references (dynamic holes). However, Chrome and Firefox keep unclosed ReadableStreams with pending reads as native GC roots, preventing the stream — and the entire FlightResponse captured in the reader.read().then(progress) closure chain — from being garbage-collected.

Now that React Flight supports unstable_allowPartialStream as an option for createFromReadableStream (facebook/react#35731), we can close the stream normally. Flight will mark unresolved chunks as "halted" instead of erroring, which is the correct behavior for prefetch responses.

Also removes the now-unnecessary createUnclosingPrefetchStream wrapper from the legacy prefetch path in fetch-server-response.ts.

closes #89485

@unstubbable unstubbable force-pushed the hl/unclosed-streams-leak branch from dc3cf74 to 08bd7d0 Compare February 6, 2026 18:21
@nextjs-bot
Copy link
Copy Markdown
Contributor

nextjs-bot commented Feb 6, 2026

Tests Passed

@nextjs-bot
Copy link
Copy Markdown
Contributor

nextjs-bot commented Feb 6, 2026

Stats from current PR

🟢 1 improvement

Metric Canary PR Change Trend
node_modules Size 467 MB 467 MB 🟢 58.5 kB (0%) ▁▁▁▁▁
📊 All Metrics
📖 Metrics Glossary

Dev Server Metrics:

  • Listen = TCP port starts accepting connections
  • First Request = HTTP server returns successful response
  • Cold = Fresh build (no cache)
  • Warm = With cached build artifacts

Build Metrics:

  • Fresh = Clean build (no .next directory)
  • Cached = With existing .next directory

Change Thresholds:

  • Time: Changes < 50ms AND < 10%, OR < 2% are insignificant
  • Size: Changes < 1KB AND < 1% are insignificant
  • All other changes are flagged to catch regressions

⚡ Dev Server

Metric Canary PR Change Trend
Cold (Listen) 456ms 455ms ▁▁▁▁▁
Cold (Ready in log) 438ms 437ms ▁▂▁▂▂
Cold (First Request) 1.165s 1.175s ▁▅▁▅▅
Warm (Listen) 457ms 457ms ▁▁▁▁▁
Warm (Ready in log) 442ms 447ms ▁▁▁▁▁
Warm (First Request) 335ms 340ms ▁▁▁▁▁
📦 Dev Server (Webpack) (Legacy)

📦 Dev Server (Webpack)

Metric Canary PR Change Trend
Cold (Listen) 455ms 455ms ▁▁▁▁▁
Cold (Ready in log) 439ms 439ms ▆▅▃▆▂
Cold (First Request) 1.818s 1.785s ▃▃▃▃▂
Warm (Listen) 456ms 456ms ▁▁▁▁▁
Warm (Ready in log) 438ms 438ms ▄▅▃▄▂
Warm (First Request) 1.823s 1.809s ▃▃▃▃▂

⚡ Production Builds

Metric Canary PR Change Trend
Fresh Build 3.819s 3.755s ▁▁▁▁▁
Cached Build 3.826s 3.820s ▁▁▁▁▁
📦 Production Builds (Webpack) (Legacy)

📦 Production Builds (Webpack)

Metric Canary PR Change Trend
Fresh Build 13.903s 13.928s ▁▁▃▁▁
Cached Build 14.038s 13.972s ▁▁▃▁▂
node_modules Size 467 MB 467 MB 🟢 58.5 kB (0%) ▁▁▁▁▁
📦 Bundle Sizes

Bundle Sizes

⚡ Turbopack

Client

Main Bundles: **437 kB** → **437 kB** ✅ -41 B

81 files with content-based hashes (individual files not comparable between builds)

Server

Middleware
Canary PR Change
middleware-b..fest.js gzip 764 B 759 B
Total 764 B 759 B ✅ -5 B
Build Details
Build Manifests
Canary PR Change
_buildManifest.js gzip 450 B 448 B
Total 450 B 448 B ✅ -2 B

📦 Webpack

Client

Main Bundles
Canary PR Change
5528-HASH.js gzip 5.47 kB N/A -
6280-HASH.js gzip 57 kB N/A -
6335.HASH.js gzip 169 B N/A -
912-HASH.js gzip 4.53 kB N/A -
e8aec2e4-HASH.js gzip 62.5 kB N/A -
framework-HASH.js gzip 59.7 kB 59.7 kB
main-app-HASH.js gzip 256 B 254 B
main-HASH.js gzip 39.1 kB 39.1 kB
webpack-HASH.js gzip 1.68 kB 1.68 kB
262-HASH.js gzip N/A 4.53 kB -
2889.HASH.js gzip N/A 169 B -
5602-HASH.js gzip N/A 5.49 kB -
6948ada0-HASH.js gzip N/A 62.5 kB -
9544-HASH.js gzip N/A 57.6 kB -
Total 230 kB 231 kB ⚠️ +601 B
Polyfills
Canary PR Change
polyfills-HASH.js gzip 39.4 kB 39.4 kB
Total 39.4 kB 39.4 kB
Pages
Canary PR Change
_app-HASH.js gzip 194 B 194 B
_error-HASH.js gzip 183 B 180 B 🟢 3 B (-2%)
css-HASH.js gzip 331 B 330 B
dynamic-HASH.js gzip 1.81 kB 1.81 kB
edge-ssr-HASH.js gzip 256 B 256 B
head-HASH.js gzip 351 B 352 B
hooks-HASH.js gzip 384 B 383 B
image-HASH.js gzip 580 B 581 B
index-HASH.js gzip 260 B 260 B
link-HASH.js gzip 2.49 kB 2.49 kB
routerDirect..HASH.js gzip 320 B 319 B
script-HASH.js gzip 386 B 386 B
withRouter-HASH.js gzip 315 B 315 B
1afbb74e6ecf..834.css gzip 106 B 106 B
Total 7.97 kB 7.97 kB ✅ -1 B

Server

Edge SSR
Canary PR Change
edge-ssr.js gzip 126 kB 126 kB
page.js gzip 249 kB 249 kB
Total 375 kB 376 kB ⚠️ +409 B
Middleware
Canary PR Change
middleware-b..fest.js gzip 614 B 613 B
middleware-r..fest.js gzip 156 B 155 B
middleware.js gzip 33.1 kB 33.3 kB
edge-runtime..pack.js gzip 842 B 842 B
Total 34.7 kB 35 kB ⚠️ +261 B
Build Details
Build Manifests
Canary PR Change
_buildManifest.js gzip 733 B 735 B
Total 733 B 735 B ⚠️ +2 B
Build Cache
Canary PR Change
0.pack gzip 3.84 MB 3.85 MB 🔴 +7.72 kB (+0%)
index.pack gzip 103 kB 103 kB
index.pack.old gzip 103 kB 104 kB 🔴 +1.61 kB (+2%)
Total 4.05 MB 4.06 MB ⚠️ +9.15 kB

🔄 Shared (bundler-independent)

Runtimes
Canary PR Change
app-page-exp...dev.js gzip 315 kB 315 kB
app-page-exp..prod.js gzip 167 kB 167 kB
app-page-tur...dev.js gzip 315 kB 315 kB
app-page-tur..prod.js gzip 167 kB 167 kB
app-page-tur...dev.js gzip 312 kB 312 kB
app-page-tur..prod.js gzip 166 kB 166 kB
app-page.run...dev.js gzip 312 kB 312 kB
app-page.run..prod.js gzip 166 kB 166 kB
app-route-ex...dev.js gzip 70.5 kB 70.5 kB
app-route-ex..prod.js gzip 49 kB 49 kB
app-route-tu...dev.js gzip 70.5 kB 70.5 kB
app-route-tu..prod.js gzip 49 kB 49 kB
app-route-tu...dev.js gzip 70.1 kB 70.1 kB
app-route-tu..prod.js gzip 48.8 kB 48.8 kB
app-route.ru...dev.js gzip 70.1 kB 70.1 kB
app-route.ru..prod.js gzip 48.7 kB 48.7 kB
dist_client_...dev.js gzip 324 B 324 B
dist_client_...dev.js gzip 326 B 326 B
dist_client_...dev.js gzip 318 B 318 B
dist_client_...dev.js gzip 317 B 317 B
pages-api-tu...dev.js gzip 43.2 kB 43.2 kB
pages-api-tu..prod.js gzip 32.9 kB 32.9 kB
pages-api.ru...dev.js gzip 43.1 kB 43.1 kB
pages-api.ru..prod.js gzip 32.8 kB 32.8 kB
pages-turbo....dev.js gzip 52.5 kB 52.5 kB
pages-turbo...prod.js gzip 39.4 kB 39.4 kB
pages.runtim...dev.js gzip 52.5 kB 52.5 kB
pages.runtim..prod.js gzip 39.3 kB 39.3 kB
server.runti..prod.js gzip 62.7 kB 62.7 kB
Total 2.8 MB 2.8 MB ✅ -138 B
📝 Changed Files (8 files)

Files with changes:

  • app-page-exp..ntime.dev.js
  • app-page-exp..time.prod.js
  • app-page-tur..ntime.dev.js
  • app-page-tur..time.prod.js
  • app-page-tur..ntime.dev.js
  • app-page-tur..time.prod.js
  • app-page.runtime.dev.js
  • app-page.runtime.prod.js
View diffs
app-page-exp..ntime.dev.js

Diff too large to display

app-page-exp..time.prod.js
failed to diff
app-page-tur..ntime.dev.js

Diff too large to display

app-page-tur..time.prod.js
failed to diff
app-page-tur..ntime.dev.js

Diff too large to display

app-page-tur..time.prod.js

Diff too large to display

app-page.runtime.dev.js

Diff too large to display

app-page.runtime.prod.js

Diff too large to display

@unstubbable unstubbable force-pushed the hl/unclosed-streams-leak branch 2 times, most recently from 6777d99 to bd2abb5 Compare February 9, 2026 11:33
Previously, `createPrefetchResponseStream` intentionally never called
`controller.close()` on the wrapper stream, to prevent React Flight from
erroring on unresolved references (PPR dynamic holes). However, Chrome
and Firefox keep unclosed ReadableStreams with pending reads as native GC
roots, preventing the stream — and the entire FlightResponse captured in
the `reader.read().then(progress)` closure chain — from being collected.

Now that React Flight supports `unstable_allowPartialStream`, we can
close the stream normally. Flight will mark unresolved chunks as
"halted" instead of erroring, which is the correct behavior for prefetch
responses.

Also removes the now-unnecessary `createUnclosingPrefetchStream` wrapper
from the legacy prefetch path in `fetch-server-response.ts`.
@unstubbable unstubbable force-pushed the hl/unclosed-streams-leak branch from bd2abb5 to 168b8ff Compare February 9, 2026 19:37
@unstubbable unstubbable changed the title [wip] Avoid using unclosed streams in the browser Avoid using unclosing prefetch streams in the browser Feb 9, 2026
@unstubbable unstubbable marked this pull request as ready for review February 9, 2026 21:57
@unstubbable unstubbable merged commit 839fe54 into canary Feb 9, 2026
269 of 281 checks passed
@unstubbable unstubbable deleted the hl/unclosed-streams-leak branch February 9, 2026 22:30
unstubbable added a commit that referenced this pull request Feb 10, 2026
Follow-up to #89610. Adds an e2e test that detects linear heap growth
caused by unclosed prefetch response streams. The test cycles through
mounting/unmounting links to trigger repeated prefetches and LRU
evictions, then uses CDP heap profiling with linear regression to verify
the heap plateaus rather than growing steadily.
unstubbable added a commit that referenced this pull request Feb 10, 2026
…9756)

Follow-up to #89610.

Adds an e2e test that detects linear heap growth caused by unclosed
prefetch response streams. The test cycles through mounting/unmounting
links to trigger repeated prefetches and LRU evictions, then uses CDP
heap profiling with linear regression to verify the heap plateaus rather
than growing steadily.


![heap-growth-chart](https://github.com/user-attachments/assets/6151c0e4-7ae1-4526-b094-8d76154be664)
@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Feb 24, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants