You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
weinand opened this issue
Aug 15, 2017
· 5 comments
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesimportantIssue identified as high-priorityverifiedVerification succeeded
VS Code: Insiders with "inspector" based EH debugging
OS: all
Pressing the "Restart" button on the debug floating window restarts the EH process just fine but in many cases results in a second debug session which makes the session drop down appear on the debug floating window.
Most likely this is a timing issue: a new session appears before the old session has terminated.
The text was updated successfully, but these errors were encountered:
weinand
added
bug
Issue identified by VS Code Team member as probable bug
debug
Debug viewlet, configurations, breakpoints, adapter issues
labels
Aug 15, 2017
It seems to think that the first process never terminated. I can't tell whether the debug adapter is doing anything wrong. Let me know if you need anything from me. I'm OOF next week.
I've seen the same problem (less frequently) with "legacy" EH debugging, so I don't think this is a specific "inspector" problem. Most likely this is a timing issue: the "inspector" debugger is faster and hits the problem more often. I will investigate...
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesimportantIssue identified as high-priorityverifiedVerification succeeded
Pressing the "Restart" button on the debug floating window restarts the EH process just fine but in many cases results in a second debug session which makes the session drop down appear on the debug floating window.
Most likely this is a timing issue: a new session appears before the old session has terminated.
FYI @roblourens
The text was updated successfully, but these errors were encountered: