Skip to content
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

Incomplete callstack on startup exceptions in windows #4379

Closed
javiercn opened this issue Jan 28, 2022 · 1 comment
Closed

Incomplete callstack on startup exceptions in windows #4379

javiercn opened this issue Jan 28, 2022 · 1 comment

Comments

@javiercn
Copy link
Member

We discovered this in the context of investigating a Blazor issue that manifested on app startup. While looking at the callstack on VS it showed incomplete information (as shown below). I believe this is a runtime issue and has nothing to do with Blazor.

See the referenced issue below for details

Gave this a try, it seems that the call stack is incomplete

   at Microsoft.AspNetCore.Components.Routing.Router.Refresh(Boolean isNavigationIntercepted)

Originally posted by @javiercn in #3695 (comment)

@javiercn
Copy link
Member Author

Nevermind, I tried again on VS and this time it worked, not sure what happened before

@ghost ghost locked as resolved and limited conversation to collaborators Feb 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant