microsoft / microsoft/vscode-cpptools

Language server repeatably crashed with nRF Connect SDK.

Open
#13,724 2 comments 0 reactions 1 assignee View on GitHub

@sean-mcmanus is already working on this.

Since Jun 24, 2025.

bug fixed Language Service reliability
Dominant language
TypeScript
Stars
6.2k
Forks
1.7k
Avg merge
14h 46m
Merged PRs (30d)
61

Description

Environment
  • OS and Version: MacOS 15.5
  • VS Code Version: 1.101.1 (Universal)
  • C/C++ Extension Version: 1.25.3
  • If using SSH remote, specify OS of remote machine: Not a remote environment
Bug Summary and Steps to Reproduce

Bug Summary:

I'm working with nRF Connect SDK with cpptools.

I think It commonly occurs when code completion is working.

Configuration and Logs
# cpptools crash call stack


cpptools
2025. 6. 24. 오전 11:06:00
SIGSEGV
browse_engine::query_translation_unit_source(msvc::canonicalized_file_path_t const&, msvc::canonicalized_file_path_t&, std::vector<msvc::canonicalized_file_path_t, std::allocator<msvc::canonicalized_file_path_t>>*) + 592
intellisense_client_manager::find_existing_intellisense_client(msvc::locked_object<intellisense_client_manager::maps, std::recursive_mutex, std::unique_lock> const&, msvc::canonicalized_file_path_t const&, bool, bool, bool, bool&, msvc::canonicalized_file_path_t&, std::vector<msvc::canonicalized_file_path_t, std::allocator<msvc::canonicalized_file_path_t>>&, bool&, bool&) + 1564
_ZN4msvc16thread_manager_t10queue_itemIZN27intellisense_client_manager27acquire_intellisense_clientERKNS_25canonicalized_file_path_tERK35acquire_intellisense_client_optionsONSt3__18functionIFvO29intellisense_client_referenceEEEPS3_RKNSA_IFbvEEEE3 + 240
msvc::thread_manager_t::do_work(unsigned int) + 512
msvc::thread_helper_t::thread_entry(void*) + 32
Other Extensions
  • nRF Connect for VS Code
    • version: 2025.5.152
Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.