-
Notifications
You must be signed in to change notification settings - Fork 38.4k
Closed
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesDebug viewlet, configurations, breakpoints, adapter issuesinsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code InsidersverifiedVerification succeededVerification succeeded
Milestone
Description
Does this issue occur when all extensions are disabled?: Yes/No
- VS Code Version: 1.63
- OS Version: Windows 10
When debugging is started, the debug console does not work properly.
In the video, when debugging is started in version 1.59, a record appears in the debug console, but only loading appears in version 1.63, and nothing is done.
However, once you click on the call stack, it works normally, or when the brake point works, it works normally like version 1.59.
Even if you erase all VS codes and reinstall them, the problem is the same.
This problem has appeared since version 1.60, but I don't know if it's a bug. Is there a solution?
1.59.mp4
1.63.mp4
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesDebug viewlet, configurations, breakpoints, adapter issuesinsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code InsidersverifiedVerification succeededVerification succeeded