René's URL Explorer Experiment


Title: core: hydration retains the first routed SSR DOM through segmentHeads after navigation · Issue #72010 · angular/angular · GitHub

Open Graph Title: core: hydration retains the first routed SSR DOM through segmentHeads after navigation · Issue #72010 · angular/angular

X Title: core: hydration retains the first routed SSR DOM through segmentHeads after navigation · Issue #72010 · angular/angular

Description: Which @angular/* package(s) are the source of the bug? core Is this a regression? Yes Description In Angular 22.2.6, the DOM of the initially server-rendered routed component remains in memory after navigating away from that route. The c...

Open Graph Description: Which @angular/* package(s) are the source of the bug? core Is this a regression? Yes Description In Angular 22.2.6, the DOM of the initially server-rendered routed component remains in memory afte...

X Description: Which @angular/* package(s) are the source of the bug? core Is this a regression? Yes Description In Angular 22.2.6, the DOM of the initially server-rendered routed component remains in memory afte...

Opengraph URL: https://github.com/angular/angular/issues/72010

X: @github

direct link

Domain: github.com


Hey, it has json ld scripts:
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"core: hydration retains the first routed SSR DOM through segmentHeads after navigation","articleBody":"### Which @angular/* package(s) are the source of the bug?\n\ncore\n\n### Is this a regression?\n\nYes\n\n### Description\n\nIn Angular 22.2.6, the DOM of the initially server-rendered routed component remains in memory after navigating away from that route.\n\nThe component’s `ngOnDestroy()` runs and its host is disconnected from the document, but the root view’s hydration data still holds a strong reference to it:\n\nRoot component LView → LView[HYDRATION] → segmentHeads[0] → detached initial route component host → its DOM subtree\n\nForced garbage collection does not release the subtree.\n\n### Reproduction\n\nI reproduced this in a minimal application with:\n\n- A root component containing only `\u003crouter-outlet />`.\n- Route `/`, rendering a component with 1,000 paragraphs.\n- Route `/b`, rendering another component with one paragraph.\n- SSR and `provideClientHydration()`.\n\nThere are no third-party widgets, application services, template event listeners, i18n blocks, `@defer` blocks, or custom route reuse strategy.\n\nBefore bootstrap, I stored only a `WeakRef` to the original SSR component host. After bootstrap, I verified that hydration reused that exact node.\n\nI then navigated to `/b`, waited for application stability and browser tasks, and forced garbage collection through CDP’s `HeapProfiler.collectGarbage`. I repeated this across four navigation cycles.\n\n### Actual behavior\n\n| Configuration | Original SSR host retained after navigation and GC |\n|---|---|\n| `provideClientHydration()` | Yes, all four cycles |\n| `provideClientHydration(withNoIncrementalHydration())` | Yes, all four cycles |\n| No hydration providers | No; the original SSR DOM is replaced at bootstrap |\n\nIn both hydrated configurations:\n\n- `ngOnDestroy()` runs.\n- The original host has `isConnected === false`.\n- `segmentHeads` still references the original host.\n- The original host survives forced garbage collection.\n\nSubsequent client-created instances were collected in the recorded run. This appears to be bounded retention of the initial SSR subtree rather than an unbounded leak on every navigation.\n\nThe no-hydration case is a control: the original SSR DOM is replaced during bootstrap, so it is not a like-for-like measurement of the later client-created DOM.\n\n### Expected behavior\n\nOnce the initially hydrated routed component has been destroyed, obsolete hydration bookkeeping in a surviving ancestor view should not prevent its DOM from being garbage-collected.\n\n### Investigation\n\nIn the installed Angular 22.2.6 code, `setSegmentHead()` stores strong DOM references.\n\nThe inspected cleanup path clears i18n hydration data and traverses child views and containers, but leaves `segmentHeads` in place.\n\nAny cleanup fix would need to preserve metadata still required by pending incremental hydration.\n\nThe diagnostic code only reads Angular internals; it does not modify them. DOM nodes were not logged, returned as DevTools handles, or retained through element selection. No performance traces were recorded.\n\n### Please provide a link to a minimal reproduction of the bug\n\n_No response_\n\n### Please provide the exception or error you saw\n\n```true\n\n```\n\n### Please provide the environment you discovered this bug in (run `ng version`)\n\n```true\nAngular packages: 22.2.6 (core, common, compiler, platform-browser, platform-server, router)\nNode.js:         24.22.1\nOS / arch:       macOS / arm64\nChrome:          157.0.8103.51 (headless)\nPlaywright:      1.62.1\nesbuild:         0.28.2\nRxJS:            7.8.2\nChange detection: zoneless\nRendering:       SSR followed by client hydration\nCompilation:     JIT, enableProdMode(), browser ngDevMode=false\n\n\nThis standalone harness does not use the Angular CLI or an AOT production build.\nThe same retention path was originally observed in an application production\nbuild; the attached evidence is from the isolated JIT reproduction above.\n```\n\n### Anything else?\n\n[Event replay issue #66506](https://github.com/angular/angular/issues/66506)\ndescribes a different retention path. This report remains reproducible with\nincremental hydration disabled and with no event listeners, so disabling event\nreplay does not resolve the observed `segmentHeads` retention.","author":{"url":"https://github.com/Rambuto","@type":"Person","name":"Rambuto"},"datePublished":"2026-11-12T16:41:38Z","url":"https://github.com/angular/angular/issues/72010"}

react-profiling0
react-import-mapreact,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322
route-pattern/_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format)
route-controllervoltron_issues_fragments
route-actionissue_layout
fetch-noncev2:272ddc08-36d9-4374-e24b-8755ff5feca3
current-catalog-service-hash81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114
request-id9C3A:19B6A2:FEA3E3:150F682:6B01DB9C
html-safe-nonce868a287a649abe6feff926c5ae4341684ac640862a4a80f585274d2f6d7c0fd7
visitor-payloadeyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI5QzNBOjE5QjZBMjpGRUEzRTM6MTUwRjY4Mjo2QjAxREI5QyIsInZpc2l0b3JfaWQiOiI3NDY0NDc0NTI1OTYzNTA4NjM2IiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0=
visitor-hmaced228b935e3aca19c3b928fa78dfa259b13443f05dc0f95b20fc44f08f556a34
hovercard-subject-tagissue:6354520931
github-keyboard-shortcutsrepository,issues,copilot
google-site-verificationApib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I
octolytics-urlhttps://collector.github.com/github/collect
analytics-location///voltron/issues_fragments/issue_layout
fb:app_id1401488693436528
apple-itunes-appapp-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/angular/angular/72010/issue_layout
twitter:imagehttps://opengraph.githubassets.com/30da04f49df1fc89af2520fb7e4273cfc826cbd895191cdcea2853ad4f1ca072/angular/angular/issues/72010
twitter:cardsummary_large_image
og:imagehttps://opengraph.githubassets.com/30da04f49df1fc89af2520fb7e4273cfc826cbd895191cdcea2853ad4f1ca072/angular/angular/issues/72010
og:image:altWhich @angular/* package(s) are the source of the bug? core Is this a regression? Yes Description In Angular 22.2.6, the DOM of the initially server-rendered routed component remains in memory afte...
og:image:width1200
og:image:height600
og:site_nameGitHub
og:typeobject
og:author:usernameRambuto
hostnamegithub.com
expected-hostnamegithub.com
Nonecc5dfdd32f62ebd3223cab3af3aa2b268d3605218237326a48a99d1efd89495c
turbo-cache-controlno-preview
go-importgithub.com/angular/angular git https://github.com/angular/angular.git
octolytics-dimension-user_id139426
octolytics-dimension-user_loginangular
octolytics-dimension-repository_id24195339
octolytics-dimension-repository_nwoangular/angular
octolytics-dimension-repository_publictrue
octolytics-dimension-repository_is_forkfalse
octolytics-dimension-repository_network_root_id24195339
octolytics-dimension-repository_network_root_nwoangular/angular
turbo-body-classeslogged-out env-production page-responsive
disable-turbofalse
browser-stats-urlhttps://api.github.com/_private/browser/stats
browser-errors-urlhttps://api.github.com/_private/browser/errors
release8c77c9e8439031ad54c75a250694842892f693e1
ui-targetfull
theme-color#1e2327
color-schemelight dark
react-app-nameissues

Links:

Skip to contenthttps://github.com/angular/angular/issues/72010#start-of-content
https://github.com/
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fangular%2Fangular%2Fissues%2F72010
GitHubRepository hosting, code review, and collaborationhttps://github.com/platform
CopilotAI coding agent for tasks, projects, and automated workhttps://github.com/features/copilot
ActionsCI/CD and automationhttps://github.com/features/actions
Code QualityQuality analysis, fixes, and enforcementhttps://github.com/features/code-quality
CodespacesCloud development environmentshttps://github.com/features/codespaces
Code SecurityVulnerability detection and remediationhttps://github.com/security/advanced-security/code-security
Secret ProtectionSecret scanning and leak preventionhttps://github.com/security/advanced-security/secret-protection
All Featureshttps://github.com/features
Documentationhttps://docs.github.com/en
Traininghttps://learn.github.com/skills
Certificationshttps://learn.github.com/credentials
Build with Copilothttps://github.com/features/ai
Customize Copilothttps://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot/customize-copilot-overview
Integrationshttps://github.com/marketplace
Trending reposhttps://github.com/trending
GitHub Sponsorshttps://github.com/open-source/sponsors
Developer articleshttps://github.com/resources/articles
ChangelogYour source for the latest features, improvements, and fixes across GitHub products, all in one place.https://github.blog/changelog/
Enterpriseshttps://github.com/enterprise
Teamhttps://github.com/team
Startupshttps://github.com/enterprise/startups
Nonprofitshttps://github.com/solutions/industry/nonprofits
Healthcarehttps://github.com/solutions/industry/healthcare
Financial serviceshttps://github.com/solutions/industry/financial-services
Manufacturinghttps://github.com/solutions/industry/manufacturing
Governmenthttps://github.com/solutions/industry/government
See all industrieshttps://github.com/solutions/industry
Why GitHubhttps://github.com/why-github
Customer Storieshttps://github.com/customer-stories
Business insightshttps://github.com/solutions/executive-insights
Trust Centerhttps://github.com/trust-center
GitHub Advanced SecurityEnterprise-grade code securityhttps://github.com/security/advanced-security
Copilot for businessEnterprise-grade AI featureshttps://github.com/features/copilot/copilot-business
Premium SupportEnterprise-grade 24/7 supporthttps://github.com/enterprise/premium-support
Documentationhttps://docs.github.com/en
Resource centerhttps://github.com/resources
Bloghttps://github.blog/
Events & webinarshttps://github.com/resources/events
Community Forumhttps://github.com/orgs/community/discussions
Customer Storieshttps://github.com/customer-stories
Integrationshttps://github.com/marketplace
Customer supporthttps://help.github.com/
Traininghttps://learn.github.com/skills
GitHub Statushttps://www.githubstatus.com/
Abouthttps://github.com/about
Partnershttps://github.com/partners
Changeloghttps://github.blog/changelog/
GitHub UniverseThe event for developers, by developers — talks, workshops, and what’s next for GitHub.https://githubuniverse.com/
Pricinghttps://github.com/pricing
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fangular%2Fangular%2Fissues%2F72010
Sign uphttps://github.com/signup?ref_cta=Sign+up&ref_loc=header+logged+out&ref_page=%2F%3Cuser-name%3E%2F%3Crepo-name%3E%2Fvoltron%2Fissues_fragments%2Fissue_layout&source=header-repo&source_repo=angular%2Fangular
Reloadhttps://github.com/angular/angular/issues/72010
Reloadhttps://github.com/angular/angular/issues/72010
Reloadhttps://github.com/angular/angular/issues/72010
angularhttps://github.com/angular
angularhttps://github.com/angular/angular
Codehttps://github.com/angular/angular
Issues835 (835)https://github.com/angular/angular/issues
Pull requests142 (142)https://github.com/angular/angular/pulls
Discussionshttps://github.com/angular/angular/discussions
Actionshttps://github.com/angular/angular/actions
Projectshttps://github.com/angular/angular/projects
Security and quality40 (40)https://github.com/angular/angular/security
Insightshttps://github.com/angular/angular/insights
https://github.com/angular/angular
New issuehttps://github.com/login?return_to=https://github.com/angular/angular/issues/72010
New issuehttps://github.com/login?return_to=https://github.com/angular/angular/issues/72010
core: hydration retains the first routed SSR DOM through segmentHeads after navigationhttps://github.com/angular/angular/issues/72010#top
area: coreIssues related to the framework runtimehttps://github.com/angular/angular/issues?q=state%3Aopen%20label%3A%22area%3A%20core%22
needsTriagehttps://github.com/angular/angular/milestone/83
https://github.com/Rambuto
Rambutohttps://github.com/Rambuto
on Nov 12, 2026https://github.com/angular/angular/issues/72010#issue-6354520931
Event replay issue #66506https://github.com/angular/angular/issues/66506
angular-robothttps://github.com/apps/angular-robot
area: coreIssues related to the framework runtimehttps://github.com/angular/angular/issues?q=state%3Aopen%20label%3A%22area%3A%20core%22
on Nov 12, 2026https://github.com/angular/angular/issues/72010#event-35937101889
angular-robothttps://github.com/apps/angular-robot
needsTriagehttps://github.com/angular/angular/milestone/83
on Nov 12, 2026https://github.com/angular/angular/issues/72010#event-35937105237
https://github.com/seragAhmed
seragAhmedhttps://github.com/seragAhmed
on Nov 13, 2026https://github.com/angular/angular/issues/72010#issuecomment-6847317705
Sign up for freehttps://github.com/signup?return_to=https://github.com/angular/angular/issues/72010
Sign in to commenthttps://github.com/login?return_to=https://github.com/angular/angular/issues/72010
area: coreIssues related to the framework runtimehttps://github.com/angular/angular/issues?q=state%3Aopen%20label%3A%22area%3A%20core%22
needsTriageNo due datehttps://github.com/angular/angular/milestone/83
https://github.com
Termshttps://docs.github.com/site-policy/github-terms/github-terms-of-service
Privacyhttps://docs.github.com/site-policy/privacy-policies/github-privacy-statement
Securityhttps://github.com/security
Statushttps://www.githubstatus.com/
Communityhttps://github.community/
Docshttps://docs.github.com/
Contacthttps://support.github.com?tags=dotcom-footer

Viewport: width=device-width


URLs of crawlers that visited me.