-
Notifications
You must be signed in to change notification settings - Fork 174
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
Moved from here.
Versions
VSCode Version:
Version: 1.46.0 (system setup)
Commit: a5d1cc28bb5da32ec67e86cc50f84c67cc690321
Date: 2020-06-10T09:03:20.462Z
Electron: 7.3.1
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.19041
OS Version:
Microsoft Windows 10 Pro 10.0.19041 Build 19041
Extensions installed
- DavidAnson.vscode-markdownlint@0.36.0
- donjayamanne.githistory@0.6.5
- eamodio.gitlens@10.2.2
- ExodiusStudios.comment-anchors@1.7.1
- Gimly81.matlab@2.0.0
- GitHub.vscode-pull-request-github@0.16.1
- lextudio.restructuredtext@128.0.0
- ms-azuretools.vscode-docker@1.2.1
- ms-python.python@2020.5.86806
- ms-vscode-remote.remote-wsl@0.44.2
- ms-vscode.powershell@2020.6.0
- vscode-icons-team.vscode-icons@10.1.1
Steps to Reproduce:
- Clone this repo.
- Place a breakpoint here.
- F5, Debug Python File run_this.py.
Does this issue occur when all extensions are disabled?: Yes/No
One probably can't debug without Python extension.
Current result:
Once the breakpoint is reached, note that Variables, Locals to the top left of the screen displays a rolling animation as if it were trying to resolve local variables.
After a while the debug is terminated abnormally.
Extra information
- Looks somewhat related to this.
- It is interesting to note that this behavior is also happening with LiClipse 6.0.0.201910251202
Metadata
Metadata
Labels
bugSomething isn't workingSomething isn't working