-
Notifications
You must be signed in to change notification settings - Fork 18k
Debug Excessively Slow Stepping Through Code #66173
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
Comments
Since I also recently upgraded to VS Code 1.87, I tried going back to version 1.86 but that did not help either. |
sounds like an issue for the debugger (delve?) and not the go project. |
Not sure if this changes your thinking at all but this post was just added to the issue I logged under delve. Not sure if this puts the ball back in your court, VS Code's court, or somewhere else but an issue that is potentially "fixed" by switching to a preview version of the Go extension seems concerning. Thoughts? For what it's worth, switching to Go Nightly did NOT resolve the issue for me, nor did disabling all anti-virus. |
Go version
1.22.1
Output of
go env
in your module/workspace:What did you do?
Stepped through Go code in VS Code.
What did you see happen?
Instead of each step being almost instantaneous as usual, each step takes anywhere from 2-3 seconds for a 2 line application, to 12-13 seconds for a larger application.
I am not certain what triggered it, though it was shortly after upgrading to v1.22.1 that I noticed it.
If I just run the app in VS Code (assuming there are no errors), it runs fast as usual, this only occurs when stepping through the code.
I moved back down to v1.21.8 to see if it was related to my recent upgrade but the issue remained, so I moved back up to 1.22.1.
Since I saw no other issues like this reported, this is likely something unique to me but I even tried completely uninstalling and reinstalling Go with no improvement and nothing else changed in the timeframe this occurred.
What did you expect to see?
Each step occurring almost instantly as it always has in the past.
The text was updated successfully, but these errors were encountered: