microsoft / microsoft/vscode-dotnettools
Restore blocks key strokes and menu actions
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 321
- Forks
- 54
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 2
Description
Type: Bug
My repro steps are the following:
- Clone https://github.com/dotnet/roslyn
- Open the folder in VS Code
- Open a project file
- Wait for implicit restore to trigger for the Solution
A few seconds after the restore starts the VS Code instances becomes unusable. Key strokes are not processed, menus clicks trigger no action, etc ... The UI is still active in that I can click on things but no events happen.
Once restore completes there is still a bit of a pause, usually over by 30 seconds, and then suddenly all the actions I've done are processed immediately. The keystrokes play out and menu actions occur. It's like there is a pause in the event processing system related to restore and once that is done everything begins functioning again.
This happens whenever I take an action that impacts restore. This means VS code is effectively unusable when I'm doing infrastructure work because editting project files can trigger restore which quickly locks up VS Code.
Extension version: 0.1.83
VS Code version: Code 1.79.0 (b380da4ef1ee00e224a15c1d4d9793e27c2b6302, 2023-06-07T14:26:35.552Z)
OS version: Windows_NT x64 10.0.22621
Modes:
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz (12 x 3192) |
| GPU Status | 2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled |
| Load (avg) | undefined |
| Memory (System) | 63.85GB (23.56GB free) |
| Process Argv | . --crash-reporter-id dd52e15f-4224-49d1-8e56-51f8f0da08b2 |
| Screen Reader | no |
| VM | 0% |
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
vscccc:30610679
3biah626:30602489
pyind779:30671433
89544117:30613380
pythonsymbol12:30671437
showlangstatbar:30737416
vsctsb:30748421
pythonms35:30701012
03d35959:30757346
7ij38806:30736111
pythonfmttext:30731395
pythoncmv:30756943
fixshowwlkth:30730052
showsbindicator:30760979
pythongtdpath:30739704
dh2dc718:30763024
pythonnosm12tcf:30757130
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the freeze by opening a project from the dotnet/roslyn repository in VS Code and waiting for implicit solution restore. Observe whether keyboard input and menu actions remain blocked during and after restore; done means the VS Code UI stays responsive while restore-related actions complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100