fix(@angular/ssr): avoid retaining rendered HTML in memory post-request#31278
Merged
alan-agius4 merged 1 commit intoangular:mainfrom Sep 23, 2025
Merged
fix(@angular/ssr): avoid retaining rendered HTML in memory post-request#31278alan-agius4 merged 1 commit intoangular:mainfrom
alan-agius4 merged 1 commit intoangular:mainfrom
Conversation
9099c4d to
3d8e0af
Compare
4f42a51 to
4386931
Compare
The previous implementation for server-side rendering could lead to memory leaks where the rendered HTML content was not properly garbage-collected after the HTTP request was fulfilled. This was caused by inefficiencies in the critical CSS caching and how the response stream was handled. This commit addresses the issue by: 1. Refactoring the `criticalCssLRUCache` to store `Uint8Array` directly and use a more robust caching strategy. 2. Using the request URL as the cache key to prevent storing multiple cache entries for the same resource. 3. Ensuring the response stream controller enqueues the final HTML as a `Uint8Array`, avoiding unnecessary string conversions and dangling references. These changes prevent the SSR response from being retained in memory, improving the stability and performance of the server. Closes angular#31277
4386931 to
a4d1613
Compare
hybrist
approved these changes
Sep 23, 2025
Collaborator
Author
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The previous implementation for server-side rendering could lead to memory leaks where the rendered HTML content was not properly garbage-collected after the HTTP request was fulfilled.
This was caused by inefficiencies in the critical CSS caching and how the response stream was handled. This commit addresses the issue by:
criticalCssLRUCacheto storeUint8Arraydirectly and use a more robust caching strategy.Uint8Array, avoiding unnecessary string conversions and dangling references.These changes prevent the SSR response from being retained in memory, improving the stability and performance of the server.
Closes #31277