You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
cpptools crash - The language server crashed. Restarting... #10651
Isolated examples that reproduce a crash and can be shared with us directly.
If you're experiencing a crash, any of the above information could be extremely useful to us to investigate and fix it. Please consider opening a new issue in this repo. Or, add a comment on this issue.
I'm pinning this issue, to make this more obvious to users who might be browsing our repo due to experiencing a crash.
Hristo Hristov (@H-G-Hristov) Yes, but that issue mentions a work around via running lldb -p <processId>, then continue (assume it gets into a stopped state), and then repro the crash, and use bt to get the full stack of the crashing thread (maybe bt all if bt isn't sufficient for some reason).
Reopening. The intent of this issue was to be pinned so users experiencing a crash can find the issue and easily find instructions. I'd like to keep this open and pinned for now.
Isolated examples that reproduce a crash and can be shared with us directly.
If you're experiencing a crash, any of the above information could be extremely useful to us to investigate and fix it. Please consider opening a new issue in this repo. Or, add a comment on this issue.
I'm pinning this issue, to make this more obvious to users who might be browsing our repo due to experiencing a crash.
Since the last update, from 1.23.6 to 1.24.5, I have been experiencing repeated crashes from the language server. Here is the crash call stack:
A C/C++ extension process has crashed. The crashing process name, date/time, signal, and call stack are below -- it would be helpful to include that in a bug report at https://github.com/Microsoft/vscode-cpptools/issues.
cpptools
4/15/2025, 2:53:57 PM
SIGSEGV
…
…
read_double(unsigned char*, char const*, int)+1761
fp_string_to_float(a_float_kind, char const*, an_internal_float_value*, int*)+254
conv_float_literal(int, an_error_code*, char const**, an_error_severity*)+264
…
_Z9get_tokenv+11866
?+67
?+61
?+325
antlr::TokenBuffer::LA(unsigned int)+77
scout_parser::assign_initializer_or_pure_default_deleted(bool, a_type_specification&)+158
scout_parser::init_declarator_list_or_function_definition(a_source_point const&, a_source_point&, a_type_specification&, a_declaration_info const&)+198
_ZN12scout_parser18simple_declarationER20a_type_specificationN5antlr13TokenRefCountINS2_5TokenEEERK18a_declaration_info+2384
_ZN12scout_parser39property_or_event_or_simple_declarationER20a_type_specificationN5antlr13TokenRefCountINS2_5TokenEEERK18a_declaration_info+526
_ZN12scout_parser19general_declarationER20a_type_specificationN5antlr13TokenRefCountINS2_5TokenEEERK18a_declaration_info+1133
_ZN12scout_parser45general_declaration_with_error_recovery_innerER20a_type_specificationN5antlr13TokenRefCountINS2_5TokenEEERK18a_declaration_info+209
_ZN12scout_parser39general_declaration_with_error_recoveryER20a_type_specificationN5antlr13TokenRefCountINS2_5TokenEEERK18a_declaration_info+187
_ZN12scout_parser11declarationEN5antlr13TokenRefCountINS0_5TokenEEERK18a_declaration_infobb+844
scout_parser::declarations(bool, bool)+462
scout_parser::source_file()+253
run_tag_parser()+486
process_translation_unit(char const*, int, an_exported_template_file*)+641
cfe_main(int, char**)+122
cfe_main_exception_handler(int, char**)+13
edg_main(int, char**)+13
…
tnum > tsize
Notice that I work on a very large and complex codebase, which is mainly Fortran (and some C++). Hence, I am using this extension as a dependency of the Modern Fortran extension with the fortls language server. However, I have no idea whether the problem originates from that extension or this one.
Hello, I reported an error when opening all C language projects. They were working before, so I don't think I made any other operation Settings. The error is reported as follows:
Hello, I reported an error when opening all C language projects. They were working before, so I don't think I made any other operation Settings. The error is reported as follows:
update
After I used the update of this link, the issue was resolved. Therefore, it might be a version compatibility problem. I hope it can be solved in the expansion of the new version. Thanks.
NickLiu635 You should report crashes in a separate issue instead of this general one. Are you able to repro the crash? Did you have GitHub Copilot enabled? If so, we have a fix pending for 1.30.0 for one such crash that I think only repros if GitHub Copilot is enabled. Are you able to set "symbolSearchPath": "https://msdl.microsoft.com/download/symbols", to get a crash call stack?
A C/C++ extension process has crashed. The crashing process name, date/time, signal, and call stack are below -- it would be helpful to include that in a bug report at https://github.com/Microsoft/vscode-cpptools/issues.
cpptools
3/30/2026, 7:47:57 PM
SIGSEGV
parser::update_file_if_needed(msvc::canonicalized_file_path_t const&, bool, bool, bool, bool&, code_store::record_id_t<code_store::file_tag_t>&)+2609
browse_engine::parse_file(std::shared_ptr<workspace_folder_context> const&, msvc::canonicalized_file_path_t const&, code_store::record_id_t<code_store::file_tag_t> const&, std::unordered_set<code_store::record_id_t<code_store::file_tag_t>, std::hash<code_store::record_id_t<code_store::file_tag_t>>, std::equal_to<code_store::record_id_t<code_store::file_tag_t>>, std::allocator<code_store::record_id_t<code_store::file_tag_t>>>&, std::string const&, std::set<std::string, std::less<std::string>> const&, parser&, std::function<void (msvc::result_t)>&&, std::shared_ptr<recursive_includes_tracker> const&, bool)+1256
browse_engine::parse_file(std::shared_ptr<workspace_folder_context> const&, msvc::canonicalized_file_path_t const&, bool, std::function<void (msvc::result_t)>&&, std::shared_ptr<recursive_includes_tracker> const&, bool)+1229
_ZN16cpptools_context17handle_parse_fileEONS_19file_and_task_tokenE+880
_ZN4msvc16thread_manager_t10queue_itemIZNS_12deque_threadIN16cpptools_context19file_and_task_tokenEE5deferEOS4_EUlvE_EclEv+177
msvc::thread_manager_t::do_work(unsigned int)+575
Activity
H-G-Hristov commentedon Mar 10, 2023
Just to remind that on
macOS: #9810sean-mcmanus commentedon Mar 10, 2023
Hristo Hristov (@H-G-Hristov) Yes, but that issue mentions a work around via running
lldb -p <processId>, thencontinue(assume it gets into a stopped state), and then repro the crash, and usebtto get the full stack of the crashing thread (maybebt allifbtisn't sufficient for some reason).sean-mcmanus commentedon Mar 17, 2023
I've reproed multiple crashes. I'm tracking it with #10636 .
We may not need this issue anymore.
Colengms commentedon Apr 27, 2023
Reopening. The intent of this issue was to be pinned so users experiencing a crash can find the issue and easily find instructions. I'd like to keep this open and pinned for now.
70 remaining items
Fix cpptools crash issue
Dustin4444 commentedon Mar 28, 2025
stefabat commentedon Apr 15, 2025
Since the last update, from 1.23.6 to 1.24.5, I have been experiencing repeated crashes from the language server. Here is the crash call stack:
Notice that I work on a very large and complex codebase, which is mainly Fortran (and some C++). Hence, I am using this extension as a dependency of the Modern Fortran extension with the fortls language server. However, I have no idea whether the problem originates from that extension or this one.
sean-mcmanus commentedon Apr 15, 2025
Stefano Battaglia (@stefabat) That is being tracked by #13435 .
MondoYang commentedon May 7, 2025
Hello, I reported an error when opening all C language projects. They were working before, so I don't think I made any other operation Settings. The error is reported as follows:
[Error - 13:52:43] Server initialization failed. Message: Pending response rejected since connection got disposed Code: -32097 [Error - 13:52:43] 在过去 3 分钟内,语言服务器崩溃了 5 次。它不会重新启动。 [Error - 13:52:43] cpptools client: couldn't create connection to server. Message: Pending response rejected since connection got disposed Code: -32097vscode version:
版本: 1.99.3 (user setup)
提交: 17baf841131aa23349f217ca7c570c76ee87b957
日期: 2025-04-15T23:18:46.076Z
Electron: 34.3.2
ElectronBuildId: 11161073
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.14393
Mac dual-system Windows 10。
thanks。
MondoYang commentedon May 7, 2025
output.log
Supplement the log
MondoYang commentedon May 8, 2025
update
After I used the update of this link, the issue was resolved. Therefore, it might be a version compatibility problem. I hope it can be solved in the expansion of the new version. Thanks.
AlmondAxis987 commentedon Jun 16, 2025
Every time a C/C++ file is opened, following happens:
I am running VS Code 1.101.0 on Windows 10. Redownloaded VS Code and C/C++ extension many times. Help pls T-T
sean-mcmanus commentedon Jun 16, 2025
AlmondAxis987 What version of the C/C++ are you using? If you open an empty folder and then run the C/C++: Log Diagnostics command from the command palette, does it still crash? If not, can you attach a debugger to the cpptools.exe process (with "symbolSearchPath": "https://msdl.microsoft.com/download/symbols", set, see https://github.com/microsoft/vscode-cpptools/wiki/Attaching-debugger-to-cpptools-or-cpptools%E2%80%90srv) and then open a C++ file to get a crash call stack?
sean-mcmanus commentedon Jun 16, 2025
Stefano Battaglia (@stefabat) The crash you hit is fixed with 1.25.3.
Amirmohammad-Seifi commentedon Jul 16, 2025
Hi, you can try it
code . --inspect-brk-extensions 3456in cmds-ciprian commentedon Oct 5, 2025
NickLiu635 commentedon Dec 5, 2025
VSCode version
版本: 1.106.3 (user setup)
提交: bf9252a2fb45be6893dd8870c0bf37e2e1766d61
日期: 2025-11-25T22:28:18.024Z
Electron: 37.7.0
ElectronBuildId: 12781156
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200
C/C++ Extension v1.28.3
Crashed When formating
stack:
Windbg says:
registers;
RAX: 0000000000003680 RBX: 00000000007772E8 RCX: 0000000000000041
RDX: 0000000140A71080 RSI: 00000000048BED00 RDI: 0000000000000000
RIP: 000000014067A52E RSP: 00000000048BEAC8 RBP: 00000000048BEB69
R8: 00000000048BEBF0 R9: 00000000048BEC90 R10: 0000000028013CC8
R11: FFFFFFFFFFFFFFFF R12: 000000000073EDE0 R13: 00000000007772A0
R14: 00000000048BEF80 R15: 00000000048BEBF0
EFLAGS: 00000285 CF=1 PF=1 AF=0 ZF=0 SF=1 TF=0 IF=1 DF=0 OF=0
LastErrorValue: 0x00000000
LastStatusValue: 0x00000000
memary
dumped by .dump /ma c:\dumps\app.dmp
How Can I Upload the dump?....
UpLoad to OneDrive, zipped by 7-zip zstd http://
https://1drv.ms/u/c/FF91F6436C5E72E1/IQAAF6YK3EMDQrli6HreyPBbAfDo0UVEBvf_VT6dGTIkOzg?e=J4WyWO
BTW, When I finashed Windbg And re-format the code . It not crash again.... however,
the formated code is so ugly...
sean-mcmanus commentedon Dec 9, 2025
NickLiu635 You should report crashes in a separate issue instead of this general one. Are you able to repro the crash? Did you have GitHub Copilot enabled? If so, we have a fix pending for 1.30.0 for one such crash that I think only repros if GitHub Copilot is enabled. Are you able to set
"symbolSearchPath": "https://msdl.microsoft.com/download/symbols",to get a crash call stack?betsch85 commentedon Mar 30, 2026
and so on...