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

VS IDE - Stepping through code is flaky #110913

Closed
Sean4572435243 opened this issue Dec 23, 2024 · 3 comments
Closed

VS IDE - Stepping through code is flaky #110913

Sean4572435243 opened this issue Dec 23, 2024 · 3 comments

Comments

@Sean4572435243
Copy link

Description

I have a complex console app with lots of awaits that when stepping through the code (e.g. F10), will frequently just resume running as if I hit continue. Nothing predictable about it. Other than the awaits, it's not inherently parallel code. Setting breakpoints or clicking the little green inline play buttons works as expected every time.

Reproduction Steps

Too flaky to define reproduction steps, though it seems more reliable if I don't delay stepping forward.

Expected behavior

In my mind, F10 should work like clicking on the inline play button on the next line to execute.

Actual behavior

Will frequently and unpredictably just continue executing instead of stepping

Regression?

Honestly not sure when it started happening, feels like this has been broken for a bit and I've been hoping it would have been remedied by now, but now that we're in a AspNetCore 9, probably needs to be pointed out.

Known Workarounds

been setting breakpoints and using the inline green arrow buttons to better control step execution. Very cumbersome since if conditions have to be mentally evaluated to know where execution steps to next so I can manually step in that direction.

Configuration

Latest everything for .Net, VS 2022 and ASPNetCore 9. High-end recent Lenovo Intel.

Other information

No response

@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Dec 23, 2024
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Dec 23, 2024
@huoyaoyuan huoyaoyuan added area-Diagnostics-coreclr and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Dec 23, 2024
Copy link
Contributor

Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.

@huoyaoyuan
Copy link
Member

Duplicate to #109785, #109812, #109885, #110841

@Sean4572435243
Copy link
Author

Apolgies! There was no checkbox for me to confirm this is not a prior issue so I just didn't think about checking for priors first. I'll close my duplicate.

@dotnet-policy-service dotnet-policy-service bot removed the untriaged New issue has not been triaged by the area owner label Dec 23, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Jan 23, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants