Skip to content

Debug Watch list not available #2639

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

Closed
ebmarquez opened this issue Apr 17, 2020 · 6 comments
Closed

Debug Watch list not available #2639

ebmarquez opened this issue Apr 17, 2020 · 6 comments
Labels
Resolution-Duplicate Will close automatically.

Comments

@ebmarquez
Copy link

Issue Type: Bug

When running the debugger, the Variables: Auto section show the correct variables but the Watch list show "not available"

Extension version: 2020.4.2
VS Code version: Code 1.44.2 (ff915844119ce9485abfe8aa9076ec76b5300ddd, 2020-04-16T16:36:23.138Z)
OS version: Windows_NT x64 10.0.18363

System Info
Item Value
CPUs Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz (8 x 3408)
GPU Status 2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off_ok
webgl: enabled
webgl2: enabled
Load (avg) undefined
Memory (System) 63.92GB (36.18GB free)
Process Argv
Screen Reader no
VM 0%
[StartEditorServices.log](https://github.com/PowerShell/vscode-powershell/files/4493541/StartEditorServices.log) [vscode-powershell.log](https://github.com/PowerShell/vscode-powershell/files/4493542/vscode-powershell.log) [EditorServices.log](https://github.com/PowerShell/vscode-powershell/files/4493543/EditorServices.log)
@ghost ghost added the Needs: Triage Maintainer attention needed! label Apr 17, 2020
@JustinGrote
Copy link
Collaborator

Dupe of #2396?

@ebmarquez
Copy link
Author

Annotation 2020-04-17 073842

@ebmarquez
Copy link
Author

It might be a dup. I also noticed I can't add new Watch variables when in a debug session. :-(

@JustinGrote
Copy link
Collaborator

JustinGrote commented Apr 17, 2020

Yeah I didn't specifically mention this part of it but it is also a problem for #2396

As a workaround, the Powershell: Restart Current Session will fix it without having to reload all of vscode. It also generally only occurs for me if I use the "Stop" button on the debugger rather than running it to completion, suggesting a cleanup issue in PSES and/or omnisharp

@SydneyhSmith
Copy link
Collaborator

Thanks everyone, going to mark this as a duplicate.

@SydneyhSmith SydneyhSmith added Resolution-Duplicate Will close automatically. and removed Needs: Triage Maintainer attention needed! labels Apr 21, 2020
@ghost
Copy link

ghost commented Apr 22, 2020

This issue has been marked as duplicate and has not had any activity for 1 day. It has been closed for housekeeping purposes.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate Will close automatically.
Projects
None yet
Development

No branches or pull requests

4 participants