vscode: Since latest update I'm getting "It's taking a while to configure your breakpoints." message
Issue Type: Bug
I have a Javascipt only application, with no transpiling or conversion going on. My launch.json is like this:
{
"type": "node",
"request": "launch",
"name": "Fetch",
"program": "${workspaceFolder}/exec.js",
"args": ["fetch.js"],
"outputCapture": "std",
"skipFiles": [
"${workspaceFolder}/node_modules/**/*.js",
"${workspaceFolder}/lib/**/*.js",
"<node_internals>/**/*.js"
]
},
Exec.js is just a wrapper that executes a method in fetch.js.
Starting this program now sometimes takes a long time and I get the following warning:
It's taking a while to configure your breakpoints. You can speed this up by updating the 'outFiles' in your launch.json.
I only have a few breakpoints, nor was this causing a problem before the update. What’s changed? And why am I advised to update outFiles while I’m only running a simple javascript script?
VS Code version: Code - Insiders 1.65.0-insider (82a8bec63666b0883d9bf762ee2aaa87e9be9a3a, 2022-02-10T05:16:36.093Z) OS version: Windows_NT x64 10.0.19044 Restricted Mode: No
System Info
| Item | Value |
|---|---|
| CPUs | Intel® Core™ i7-4710HQ CPU @ 2.50GHz (8 x 2494) |
| GPU Status | 2d_canvas: enabled canvas_oop_rasterization: disabled_off gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_renderer: enabled_on video_decode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled |
| Load (avg) | undefined |
| Memory (System) | 7.89GB (2.72GB free) |
| Process Argv | –crash-reporter-id 82b0b2fc-aa31-4181-9863-56bf85ed5e36 |
| Screen Reader | no |
| VM | 0% |
A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30422396
pythontb:30258533
pythonvspyt551:30291412
pythonptprofiler:30281269
vshan820:30294714
pythondataviewer:30285072
vscod805cf:30301675
pythonvspyt200:30323110
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30404738
wslgetstartedc:30421358
vsclayoutctrt:30405800
dsvsc008:30436272
pythonvspyt640:30426300
vsbas813:30436447
vscscmwlcmc:30428972
azactmsal:30432848
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 4
- Comments: 39 (14 by maintainers)
does the trick 👍🏻
Still weird that this used to work before, but now VSCode becomes unusable after debugging without this configuration. When the
It's taking a while to configure your breakpoints.message is shown, debugging gets stuck and I have to restart VSCode to be able to use it again.We met same issue at VSCode 1.64.2, it becomes super slow to get debug started. Tried a workaround is adding outFiles in the launch.json config. Also tried go back to old VSCode 1.63.2, which doesn’t have this issue.
I’m seeing the same issue in a TypeScript monorepo. I’m transpiling the ts files for debugging on the fly using
esbuild-register, which has inline sourcemaps, so specifying the out files is off the table for me. Before the recent VSCode update, debugging worked flawlessly and without much delay.Thanks very much, this solved my problem. Apologies for the trouble!
For
ts-node, theoutFilescan be specified to point to your source files. Alternatively, you can setoutFilesto an empty array[]andresolveSourceMapLocations: nullto say “don’t scan for any sourcemaps, but also don’t restrict where sourcemaps can be resolved”.Very. We are in a monorepo
No