Sean McManus

@hediet This is important to get checked in ASAP -- otherwise the C/C++ experience is regressed with VS Code Insiders, i.e. red `#endif` appear all over the place with code...

@hediet Okay, that seems fine. What were the problems though? I was only aware of the problem with `#endif` not matching with `#ifdef` and `#ifndef` which got fixed by this...

It looks like there could be some issue with the IntelliSense process creation. For the 1st 2 logs I see "Queueing IntelliSense update, but not finish response. For the 3rd,...

If you're able to attach a debugger to the cpptools process to get call stacks when it's in a stuck state that might help (https://github.com/microsoft/vscode-cpptools/wiki/Attaching-debugger-to-cpptools-or-cpptools%E2%80%90srv).

@albertcaldas84 We spawn one cpptools-srv process per C/C++ file open -- can you just open the 1 repro file? Also, after attaching you should use the break button in the...

@jsimonlane What version of the C/C++ extension? What OS? Does the CPU processing ever end? With C_Cpp.loggingLevel set to "Debug" what logging output is shown in the C/C++ window? Are...

@justin39 The earlier post said cpptools is spinning, but your post says cpptools-srv has the issue -- which process is it? Your logging indicates a file was opened and then...

Our main thread is blocked in the didOpen waiting for a response from cpptools-srv for handle_contains. Another thread is handling an IntelliSense update (it may also be blocked on something)....

@justin39 Yeah, a repro with more files and cpptools-srv is okay, but then you'd need to somehow identify which process to attach to to get the call stack for the...

@albertcaldas84 Are you remoting to a Mac machine? I appeared to be hitting a VS Code remote bug that wouldn't let me pause the debugger to get breakpoints (I had...