microsoft / microsoft/vscode-cpptools

Language server repeatably crashed with nRF Connect SDK.

Aperta
#13,724 2 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@sean-mcmanus ci sta già lavorando.

Dal 24/6/2025.

bug fixed Language Service reliability
Lingua principale
TypeScript
Stelle
6.2k
Fork
1.7k
Merge medio
14h 46m
PR unite (30g)
61

Descrizione

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

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.