microsoft / microsoft/vscode-cpptools
Crash in code_analysis::process_async::cleanup()
Open
Nobody has claimed this yet.
bug
Language Service
regression
reliability
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
I have also this issue since some weeks.
cpptools
8/22/2024, 3:51:00 PM
SIGSEGV
code_analysis::process_async::cleanup() const+767
code_analysis::process_async::main()+1419
code_analysis::process_async_work(unsigned int, file_uri const&, std::optional<file_uri>&&, std::shared_ptr<workspace_folder_context> const&, std::shared_ptr<intellisense_client_config> const&)+103
msvc::thread_manager_t::do_work(unsigned int)+486
With the same setup I had no troubles approx. two weeks before.
Originally posted by @daniel-brosche in https://github.com/microsoft/vscode-cpptools/issues/12554#issuecomment-2305163709
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 with the reported stack trace at code_analysis::process_async::cleanup() const and follow its call from code_analysis::process_async::main(). Reproduce the SIGSEGV using the same setup described in the issue, then verify that the crash no longer occurs in that path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100