fix(@angular/ssr): avoid retaining rendered HTML in memory post-request #31278
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:
criticalCssLRUCache
to storeUint8Array
directly 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