[Bug] Frequent crashes since switching from twxs.cmake

[DaydreamCoding]

Brief Issue Summary

Frequent crashes since switching from twxs.cmake

CMake Tools Diagnostics

Frequent crashes since switching from twxs.cmake

Debug Log

Frequent crashes since switching from twxs.cmake

Additional Information

No response

[gcampbell-msft]

@DaydreamCoding This sounds like something we need to urgently address, however, we will need more information. Are you able to provide information on what is crashing? What action are you attempting to perform when this happens? Is there any log from vscode?

Any information you can provide would be great. Thanks.

[DaydreamCoding]

https://github.com/microsoft/vscode/issues/244718

It might not be this issue, I'm not sure if it's a problem with VS Code Insider or something else, but it occurred when I was building a C++ project with CMake.

Not sure how to get more logs, the probability of recurrence is very high; it easily becomes unresponsive as long as CMake information is generated, but the Release version of VSCode does not.

@gcampbell-msft

[gcampbell-msft]

Oh interesting that this only happens with VS Code Insider, I'd be curious to know what they find when the vscode team investigates the bug you linked. I will also try to find time to investigate those logs, I'm not entirely familiar with the format of those logs so it may take some time

[gcampbell-msft]

@DaydreamCoding In the meantime, it would be interesting if you could try other language service providers or languages to see if this re-occurs anywhere else

[DaydreamCoding]

When the CMake configuration process encounters an error, it can cause VS Code to become unresponsive and eventually crash, and Cursor will also

[Evelyn-001]

Thanks for your reply. According to your latest comment, it causes VS Code to become unresponsive and eventually crash. So could you please refer to document collect a dump file so that we can conduct further research with the following steps:

• Close all instances of VSCode.
• Run code --crash-reporter-directory <absolute-path> from the command line.
  • Run code-insiders instead of code if the issue is occurring on the Insiders version.
• Take the steps that lead to the crash.
• Check for a *.dmp file in that folder.
• Send the *.dmp file back to us.

We are looking forward to hearing from you. Thanks.