-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Blazor Webassembly - Debugger crashes app #66149
Comments
Thank you for filing this issue. In order for us to investigate this issue, please provide a minimalistic repro project (ideally a GitHub repo) that illustrates the problem. |
Tagging subscribers to this area: @thaystg Issue DetailsIs there an existing issue for this?
Describe the bugIf we start to debug our webassembly project, the app is crashing (With IIS Express or even without..). Any hints how we can diagnose this problem? Expected BehaviorDebugger works like expected :-). Steps To ReproduceNo response Exceptions (if any)
.NET Version6.0.2 Anything else?No response
|
@lewing FYI |
Can you please attach the Log that you can find at: Thanks for your help. |
This issue has been marked |
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsIs there an existing issue for this?
Describe the bugIf we start to debug our webassembly project, the app is crashing (With IIS Express or even without..). Any hints how we can diagnose this problem? Expected BehaviorDebugger works like expected :-). Steps To ReproduceNo response Exceptions (if any)
.NET Version6.0.2 Anything else?No response
|
We could add some error checking to that code, like https://gist.github.com/radical/0cf3dc140068c05f3c2a988ddd9d89c8 |
Sure. Do you want to open the PR? |
This issue has been automatically marked |
This issue will now be closed since it had been marked |
Is there an existing issue for this?
Describe the bug
If we start to debug our webassembly project, the app is crashing (With IIS Express or even without..).
The app works perfect if we dont attach the debugger, or if we remove the inspectUri from the launchSettings.json.
Any hints how we can diagnose this problem?
Expected Behavior
Debugger works like expected :-).
Steps To Reproduce
No response
Exceptions (if any)
Microsoft.WebAssembly.Diagnostics.DevToolsProxy[0] DevToolsProxy::Run: Exception System.AggregateException: One or more errors occurred. (Index was out of range. Must be non-negative and less than the size of the collection. (Parameter 'index')) ---> System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection. (Parameter 'index') at System.Collections.Generic.List1.get_Item(Int32 index) at Newtonsoft.Json.Linq.JContainer.GetItem(Int32 index) at Newtonsoft.Json.Linq.JArray.get_Item(Object key) at Microsoft.WebAssembly.Diagnostics.MonoProxy.AcceptEvent(SessionId sessionId, String method, JObject args, CancellationToken token) at Microsoft.WebAssembly.Diagnostics.DevToolsProxy.OnEvent(SessionId sessionId, String method, JObject args, CancellationToken token) --- End of inner exception stack trace --- at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions) at System.Threading.Tasks.Task1.GetResultCore(Boolean waitCompletionNotification) at System.Threading.Tasks.Task1.get_Result() at Microsoft.WebAssembly.Diagnostics.DevToolsProxy.Run(Uri browserUri, WebSocket ideSocket)
.NET Version
6.0.2
Anything else?
No response
The text was updated successfully, but these errors were encountered: