-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Issue Type: Bug
While debugging VS Code (using the Debug VS Code Main, Renderer & Extension Host config), I sometimes see this error:
I think it is related to the extension host dying (or restarting and the debugger loses connection to it).
Here is the debug adapter log: vscode-debugadapter.zip
VS Code version: Code - Insiders 1.42.0-insider (be9c724, 2020-01-29T05:39:07.145Z)
OS version: Windows_NT x64 10.0.19041
System Info
| Item | Value |
|---|---|
| CPUs | AMD Ryzen 9 3900X 12-Core Processor (24 x 3800) |
| GPU Status | 2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled metal: disabled_off multiple_raster_threads: enabled_on oop_rasterization: disabled_off protected_video_decode: unavailable_off rasterization: enabled skia_renderer: disabled_off surface_control: disabled_off surface_synchronization: enabled_on video_decode: enabled viz_display_compositor: enabled_on viz_hit_test_surface_layer: disabled_off webgl: enabled webgl2: enabled |
| Load (avg) | undefined |
| Memory (System) | 31.95GB (18.15GB free) |
| Process Argv | --folder-uri file:///c%3A/Users/Eric/code/microsoft/vscode |
| Screen Reader | no |
| VM | 0% |
Reactions are currently unavailable
Metadata
Metadata
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

