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

Debugging vitest with Caught Exception and Uncaught Exception enabled is very slow to start #204581

Closed
Nostras opened this issue Feb 7, 2024 · 0 comments · Fixed by microsoft/vscode-js-debug#1952
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues

Comments

@Nostras
Copy link

Nostras commented Feb 7, 2024

Type: Bug

Simply do whatever is stated by the vitest.dev writing tests:
https://vitest.dev/guide/#writing-tests

Enable Caught and Uncaught exceptions and try debugging with javascript debug console.

It takes about 20 seconds for the "file list" to load all the files.
Most of the testing was performed with vitest-dev, but problem persists when using javscript debug console.

No such problems are seen with jest or by just running it or debugging without the caught and uncaught exceptions.
Webstorm also does not have this problem, this seems to be an issue with how VSCode interacts with a vitest debug session.
Disabling caught and uncaught exceptions is often suggested when searching for this problem, but this is not an acceptable compromise.

VS Code version: Code - Insiders 1.87.0-insider (cf7ddbb, 2024-02-06T11:27:32.075Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Remote OS version: Linux x64 5.15.133.1-microsoft-standard-WSL2
Remote OS version: Linux x64 5.15.133.1-microsoft-standard-WSL2

System Info
Item Value
CPUs 12th Gen Intel(R) Core(TM) i7-12800H (20 x 2803)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: enabled_on
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
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
Load (avg) undefined
Memory (System) 63.68GB (32.94GB free)
Process Argv --crash-reporter-id 140b7763-bbfd-4465-9e0d-a566862fcae1
Screen Reader no
VM 0%
Item Value
Remote WSL: SO
OS Linux x64 5.15.133.1-microsoft-standard-WSL2
CPUs 12th Gen Intel(R) Core(TM) i7-12800H (20 x 2803)
Memory (System) 31.19GB (26.49GB free)
VM 0%
Item Value
Remote WSL: Ubuntu
OS Linux x64 5.15.133.1-microsoft-standard-WSL2
CPUs 12th Gen Intel(R) Core(TM) i7-12800H (20 x 2803)
Memory (System) 31.19GB (26.49GB free)
VM 0%
A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
vsaa593:30376534
py29gd2263:30784851
c4g48928:30535728
962ge761:30841072
pythongtdpath:30726887
welcomedialog:30812478
pythonidxpt:30768918
pythonnoceb:30776497
asynctok:30898717
dsvsc013:30777762
dsvsc014:30777825
dsvsc015:30821418
pythontestfixt:30866404
pythonregdiag2:30926734
pyreplss1:30879911
pythonmypyd1:30859725
pythoncet0:30859736
pythontbext0:30879054
accentitlementst:30870582
dsvsc016:30879898
dsvsc017:30880771
dsvsc018:30880772
d34g3935:30958346
b5d27386:30943795
fegfb526:30952798
7j2b6412:30951517
e3gdj431:30946825
ccp2r3:30958153

@roblourens roblourens assigned connor4312 and unassigned roblourens Feb 12, 2024
@connor4312 connor4312 added bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues labels Feb 12, 2024
connor4312 added a commit to microsoft/vscode-js-debug that referenced this issue Feb 26, 2024
connor4312 added a commit to microsoft/vscode-js-debug that referenced this issue Feb 26, 2024
* fix: race when stopping on node-internals exceptions

Fixes microsoft/vscode#204581

* rm debug
connor4312 added a commit to microsoft/vscode-js-debug that referenced this issue Feb 26, 2024
connor4312 added a commit to microsoft/vscode-js-debug that referenced this issue Feb 26, 2024
* fix: race when stopping on node-internals exceptions

Fixes microsoft/vscode#204581

* fix: missing files making test fail
@microsoft microsoft locked and limited conversation to collaborators Jun 10, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants