Colen Garoutte-Carson

Hi @bferguson3 . When you installed the clangd extension, it would have prompted you with something like the following:  Assuming you clicked on `Disable IntelliSense`, that would have disabled...

Hi @bferguson3 . Is it possible you missed a settings file (as Sean suggested) which still contains `C_Cpp.intelliSenseEngine` set to `Disabled`? On Mac (if no remoting is involved), I believe...

Hi @openglfreak . Thanks for reporting this. I'm able to repro the issue with VS (we share the IntelliSense implementation with VS). I've opened an issue against VS internally.

This fix for this is expected in >=1.12.1

@sean-mcmanus We have the ability to build for ARM and ARM64 Linux (using Docker and processor emulation), but you may be right about needing ARM64 Windows support in the lab...

Hi @Bestie123 . Does this issue still occur for you with 1.11.5 or 1.12.1 ? We recently addressed a crash issue specifically with llvm-project, that could have led to this...

@Bestie123 Is it possible the crash was caused by? : `clang\test\parser\parser_overflow.c` https://github.com/microsoft/vscode-cpptools/issues/9653 Without that file, I'm able to parse all of the latest code currently in the llvm-project repo. (Though,...

Please do not commit to main until corrections are made. As the loc team makes corrections, this PR will get updated.

The VS issue is here: https://developercommunity.visualstudio.com/content/problem/672813/find-all-references-performance-issues.html

Hi @Ursescu . Thanks for reporting this. Is the C/C++ extension otherwise unresponsive while this is occurring? If it's a busy lock, could you try attaching a debugger to the...