cpptools causing vscode lock ups when bringing it up to foreground

[KaeLL]

So my VSCode has been having issues with small lock-ups for months now, and I've been putting off taking a look into it because I had other more important things. But it's gotten to a point that is really bothering me.
For the last 2 weeks, I've been testing VSCode with all extensions disabled for one week, which I had no issues, and another week with only cpptools enabled, and it started to happen again.
What happens is that, in a frequency that seems to be random, upon bringing any instance of VSCode to foreground, it locks up for about ~3 seconds, and that's per instance (it also happens when switching from one VSCode instance to another).
I'm not exactly sure how to go about forcing this issue and gathering information about it. I think the information that it happens after bringing any single window of VSCode to foreground may be a clue. Not sure if perf would catch it, and it would have to monitor all instances for a long time.
I'm on Fedora 42, VSCode 1.105.1, cpptools 1.28.3.
Let me know what else I can help in debugging this.

[sean-mcmanus]

@KaeLL What process do you see using CPU when the lockup happens? Does it repro for all workspaces? Does it repro when no files are open? With C_Cpp.loggingLevel set to "Debug" what logging do you see when it repros?

Do you have enough memory free? Have you seen it repro on any other OS?

Generally, our extension has no control over the VS Code UI so I'm not sure how we could be causing this.