Fix Windows profiling navigation crash - #228
Merged
Merged
Conversation
Register the profiling viewer service in the Windows app head so Blazor can activate the Profiling page without crashing the WebView. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 30e2f0b9-3961-4a0b-85a6-8a28bc7286d8
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Navigating to Profiling on Windows failed during Blazor component activation because
ProfilingViewerServicewas missing from the Windows app's DI container, leaving the WebView unusable until restart.Register the viewer as a singleton in the Windows app head, matching the existing macOS registration and its window-owning lifetime.
Fixes: #205