microsoft / microsoft/vscode-cpptools
Debugger Freezes When Inspecting Large Array
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Type: Bug
When debugging a C++ console application in Visual Studio Code, the debugger freezes when attempting to inspect a large array (1,000,000 elements) in the "Variables" panel, even though GDB's print limit is set to 100 elements and VS Code's debug view is configured to display only the first 1,000 elements. This issue causes the debugger to become unresponsive, preventing further debugging.
Extension version: 1.26.3
VS Code version: Code 1.103.2 (6f17636121051a53c88d3e605c491d22af2ba755, 2025-08-20T16:45:34.255Z)
OS version: Windows_NT x64 10.0.26100
Modes:
A/B Experiments
vsliv368:30146709
vswsl492cf:30256860
binariesv615:30325510
vscrpc:30673769
nativeloc1:31344060
dwcopilot:31170013
dwoutputs:31242946
copilot_t_ci:31333650
e5gg6876:31282496
996jf627:31283433
pythonrdcb7:31342333
usemplatestapi:31297334
747dc170:31275177
6518g693:31334701
aj953862:31281341
nesew2to5:31336538
agentclaude:31350858
nes-set-on:31351930
6abeh943:31336334
0927b901:31350571
custommodelcf:31371783
45650338:31358607
0cj2b977:31352657
gaj49834:31362110
asdad-cf:31365767
controlchatstate:31363048
pylancealldocst:31371774
cloudbuttonc:31374191
retryenabled:31370050
search_len_ctrl:31378778
3efgi100_wstrepl:31374188
Contributor guide
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
Start by reproducing the freeze in a C++ console application with a 1,000,000-element array, using the Variables panel with GDB's print limit at 100 and the debug view limited to 1,000 elements. Compare behavior with the reported VS Code and C/C++ extension versions; done means inspecting the array no longer makes the debugger unresponsive.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100