-
Notifications
You must be signed in to change notification settings - Fork 38.2k
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 issuesverifiedVerification succeededVerification succeeded
Milestone
Description
- VSCode Version: Code 1.18.1 (929bacb, 2017-11-16T18:32:36.023Z)
- OS Version: Windows_NT x64 10.0.15063
- Extensions:
| Extension | Author (truncated) | Version |
|---|---|---|
| vscode-eslint | dba | 1.4.3 |
| EditorConfig | Edi | 0.11.1 |
| vsc-material-theme | Equ | 1.1.2 |
| JSDocTagComplete | Hoo | 0.0.2 |
| vscode-esformatter | how | 1.5.2 |
| output-colorizer | IBM | 0.1.2 |
| vscode-puglint | mrm | 2.3.0 |
| debugger-for-chrome | msj | 3.5.0 |
| code-spell-checker | str | 1.5.1 |
(2 theme extensions excluded)
Lately I've been running into this issue many times per day, but I can't see the pattern that causes this.
When I hit a breakpoint, only the top stack frame is shown. More frames are displayed once I step to the next line. However, this is not possible if the line I'm breaking on is a throw statement, which makes this an annoyance.
Restarting VS Code fixes this briefly, but VS Code will start misbehaving again shortly after.
I've had this in multiple projects in various source files, so I doubt it is related to anything specific in these projects.
What can I do to gather more insights on this?
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 issuesverifiedVerification succeededVerification succeeded
