-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release/7.0] [wasm][debugger] Fixing when trying to call mono functions in a non wasm page #77501
Conversation
Tagging subscribers to this area: @thaystg Issue DetailsBackport of #77496 to release/7.0 /cc @thaystg Customer ImpactTestingRiskIMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.
|
@thaysg When this is ready, please add the |
@thaystg can you please get a code review sign-off? |
CI failures are:
|
Approved by Tactics, signed off by code reviewer. CI failures unrelated. No OOB package authoring changes needed for this PR. Ready to merge. |
Backport of #77496 to release/7.0
/cc @thaystg
Customer Impact
The customer is trying to login in its blazor wasm app. During some redirections to other pages caused by the login process, the BrowserDebugProxy receives a new debug context from the browser and try to check if it’s a wasm app evaluating some commands, the first one works well the second one throws an exception. This is not something easy to reproduce, but sometimes while login this may happen, then the debugger crashes and the debug session is terminated.
Testing
Manually tested.
Risk
Low risk, only adding a try catch to ignore any error that we can get on RuntimeReady method, because it's not a wasm page.
IMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.