Sean McManus

Ok, so maybe keep this open until we get the translation.

@Colengms Oh, but it's been 2 weeks -- shouldn't we have gotten the string translated by now? I don't see it translated in the loc branch. But I also didn't...

It looks like the English strings (untranslated) got updated in the loc branch just 10 hours ago, so it looks like there's just some delay in the translations and we're...

It looks like we still haven't gotten the translation yet (maybe for 1.23.0).

Can you try with 1.13.2 (pre-release) -- we improved the performance in the scenario where there's a lot of compile command entries with the fix for https://github.com/microsoft/vscode-cpptools/issues/9882 . If it's...

The CMake Tools issue would only apply if you're using CMake Tools instead of compileCommands to configure. I don't know why you wouldn't be seeing a performance improvement with 1.13.2....

I'm not sure what you mean by "If i want to test just tag parsing, is it enough to remove the compile_commands.json file from the c_cpp_properties.json?". If you don't see...

There's info on how to get a call stack at https://github.com/microsoft/vscode-cpptools/wiki/Attaching-debugger-to-cpptools-or-cpptools%E2%80%90srv . However, I think we have enough repro info so I don't think we need a call stack.

@hriekehof This should be fixed with https://github.com/microsoft/vscode-cpptools/releases/tag/v1.22.0 -- let us know if you still see performance issues.

We're tracking additional performance improvements with https://github.com/Microsoft/vscode-cpptools/issues/12825 .