![]() Let me know how I can help to track down this issue. Ultimately, if that helps: we use Git in our project, with a few CMake dependencies. Usually, that happens when I'm typing some code, then vscode will just stop responding for a while. CMake langage support for Visual Studio CodeĪlso, what exactly do you mean by freezing of the editor window, do you mean:īy frozen I mean that the entire vscode instance will stop responding for a short while (from a couple of seconds to tens of seconds) while the rest of the macOS apps and the system will continue working normally.C/C++ IntelliSense, debugging, and code browsing.So far, the only C/C++ that are enabled are: Thursday Octo8:32 AM PDT by Joe Rossignol Following the release of macOS Catalina version 10.15.7, an increasing number of users have experienced an issue with a system process named '. I'm not exactly sure of what extensions are possibly causing the issue, but when the freezing occurs, I usually notice that a few vscode processes are eating the whole CPU time (mostly: either cpp-tools or sometimes the vscode renderer). ![]() In idle with around 4 tabs open, Activity Monitor shows Finder using between 60-70 CPU. It could also help to get a call stack (or perf trace) of the process that appears to be causing the issue.Īny hints on getting that call stack / perf trace for you (I'm using the homebrew version of vscode).Īnd any info on why you believe the C/C++ extension is the cause of the freezing would help. Has anyone else seen what seems like unreasonably high cpu usage for Finder.
0 Comments
Leave a Reply. |