Skip to content
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

Debug session caught exception toggle gets stuck #919

Closed
lramos15 opened this issue Feb 3, 2021 · 2 comments
Closed

Debug session caught exception toggle gets stuck #919

lramos15 opened this issue Feb 3, 2021 · 2 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Milestone

Comments

@lramos15
Copy link
Member

lramos15 commented Feb 3, 2021

Issue Type: Bug

  1. Start debugging VS Code
  2. Set it to break on caught exceptions
  3. Trigger something that causes a caught exception
  4. Uncheck the box
  5. Trigger something that causes a caught exception again
  6. 🐛 It stops at the caught exception even though the box isn't checked.

VS Code version: Code - Insiders 1.53.0-insider (e1c818a171168eedf78b62fdc7f4e3458d5dea7c, 2021-02-03T08:22:02.267Z)
OS version: Darwin x64 20.3.0

System Info
Item Value
CPUs Intel(R) Core(TM) i7-1068NG7 CPU @ 2.30GHz (8 x 2300)
GPU Status 2d_canvas: enabled
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
webgl: enabled
webgl2: enabled
Load (avg) 2, 2, 2
Memory (System) 32.00GB (5.55GB free)
Process Argv --crash-reporter-id 7170f6db-7270-442f-945e-4508c02991d4
Screen Reader no
VM 0%
Extensions (12)
Extension Author (truncated) Version
vscode-eslint dba 2.1.14
EditorConfig Edi 0.16.4
codespaces Git 0.6.1
vscode-pull-request-github Git 0.22.0
remote-containers ms- 0.158.0
remote-ssh ms- 0.63.0
remote-ssh-edit ms- 0.63.0
vscode-remote-extensionpack ms- 0.20.0
js-debug-nightly ms- 2021.2.117
vscode-github-issue-notebooks ms- 0.0.60
vscode-markdown-notebook ms- 0.0.13
debugger-for-chrome msj 4.12.12
A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368cf:30146710
vsreu685:30147344
openlogontheside:30221882
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30208930
wsl2prompt:30219162
vstry244:30244315
pythonvsdeb440:30224570
unusedpromptcf:30219165
folderexplorer:30219166
openfilemenucf:30219169
pythonvsded773:30223139
pythonvspyt600cf:30251589
core-portspanel:30233467
coreuntitledfile:30249963

@lramos15 lramos15 transferred this issue from microsoft/vscode Feb 3, 2021
@connor4312 connor4312 added the bug Issue identified by VS Code Team member as probable bug label Feb 4, 2021
@connor4312 connor4312 self-assigned this Feb 4, 2021
@connor4312 connor4312 added this to the February 2021 milestone Feb 4, 2021
@connor4312
Copy link
Member

connor4312 commented Feb 5, 2021

Having some trouble hitting this. If you can reproduce easily, can "trace": true to the Launch VS Code Internal config and share the resulting log file? Its location will be written to the Debug Console

@connor4312 connor4312 added the info-needed Issue requires more information from poster label Feb 5, 2021
@lramos15
Copy link
Member Author

lramos15 commented Feb 8, 2021

vscode-debugadapter-c18a7a94.json.gz

The exact repro I use is

  1. Launch OSS through the debugger
  2. Make an untitled file and type in it
  3. Tick break on caught exceptions
  4. Trigger Reopen Editor With, this will cause it to break on a couple of exceptions
  5. Untick the break on exception box
  6. Redo step 4
  7. 🐛 It breaks on the exceptions again

@connor4312 connor4312 removed the info-needed Issue requires more information from poster label Feb 8, 2021
@connor4312 connor4312 modified the milestones: February 2021, March 2021 Feb 26, 2021
@lramos15 lramos15 added the verified Verification succeeded label Mar 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

2 participants