Creating Windows.Forms.Form lock the debugger - v2019.11.0-preview

[ili101]

Issue Type: Bug

Add-Type -AssemblyName System.Windows.Forms
$Form = [System.Windows.Forms.Form]::new()
Set-PSBreakpoint -Variable 'Foo'
$Foo = 5

When Run in the "PowerShell Integrated Console" in any way you will get into DBG mode as expected but you cannot write anything in the console, In addition adding/removing breakpoints have no effect.
Essentially making debugging unusable.

Extension version: 2019.11.1-CI.38936
VS Code version: Code 1.40.2 (f359dd69833dd8800b54d458f6d37ab7c78df520, 2019-11-25T14:54:45.096Z)
OS version: Windows_NT x64 10.0.18362

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz (8 x 3392)
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)	15.93GB (7.72GB free)
Process Argv
Screen Reader	no
VM	67%

[SydneyhSmith]

@ili101 thanks for opening this issue, could you please also provide the logs of this? Thanks!

[ili101]

EditorServices.log

[ili101]

Still a problem on v2019.12.0-preview (v2019.12.0-stable don't have this problem)

This issue is being closed as inactive, if this issue is still occurring it will be re-opened

[rjmholt]

Output from !EEStack in windbg from a deadlock reproduced with the steps given in the issue description:

deadlock_dump.txt