fix(@angular/ssr): handle platform destruction during rendering #32263
+30
−4
Conversation
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
Fixes crash when platform/app destroys itself during the bootstrapping and stabilization phase. Previously, the code would call `applicationRef.injector` without checking if the platform was destroyed, resulting in: "Error: Injector has already been destroyed" This can occur when: - Component constructor calls `inject(PlatformRef).destroy()` - AbortSignal triggers during request handling - APP_INITIALIZER rejects and causes cleanup - Custom guard/resolver logic destroys the platform Solution: Check `applicationRef.destroyed` after `whenStable()` and return error state instead of accessing destroyed injector. Test: Added test case that destroys app in component constructor to verify graceful handling of this edge case.
alan-agius4
reviewed
Jan 12, 2026
Comment on lines
+107
to
+113
| return { | ||
| hasNavigationError, | ||
| redirectTo: undefined, | ||
| // TODO(alanagius): let's think on the content? | ||
| // or should we use `Promise.resolve('...')`? | ||
| content: () => Promise.reject(new Error('Application was destroyed during bootstrapping')), | ||
| }; |
Collaborator
There was a problem hiding this comment.
You could change the return type of this function to
): Promise<
| { hasNavigationError: boolean; redirectTo?: string; content: () => Promise<string> }
| { hasNavigationError: true }
> {and change the return to
Suggested change
| return { | |
| hasNavigationError, | |
| redirectTo: undefined, | |
| // TODO(alanagius): let's think on the content? | |
| // or should we use `Promise.resolve('...')`? | |
| content: () => Promise.reject(new Error('Application was destroyed during bootstrapping')), | |
| }; | |
| return { | |
| hasNavigationError: true | |
| }; |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes crash when platform/app destroys itself during the bootstrapping and stabilization phase. Previously, the code would call
applicationRef.injectorwithout checking if the platform was destroyed, resulting in: "Error: Injector has already been destroyed"This can occur when:
inject(PlatformRef).destroy()Solution: Check
applicationRef.destroyedafterwhenStable()and return error state instead of accessing destroyed injector.Test: Added test case that destroys app in component constructor to verify graceful handling of this edge case.