Extension locks up occasionally when switching between git branches

Brief Issue Summary

Occasionally when switching between git branches in the currently open folder (either through the VSCode UI or through the shell, it doesn’t seem to make a difference), the extension appears to get stuck doing something with cmake.

Expected:

1. Checkout a different git branch
2. The active branch changes.

Apparent Behavior:

Intermittent

1. Checkout a different git branch
2. The UI seems to be waiting for the branch to change.
3. cmake.exe and a VSCode subprocess will both be using 2 cores fully. The cmake subprocess memory usage will steadily climb up. After 10-20 minutes it’s using over 24 GB of memory and still climbing.
4. During this time no git actions can be taken since there are OS level locks held on seemingly random files preventing them from being opened or modified.

It’s unclear whether this process ever completes on its own.

CMake Tools Log

No log output observed during these events.

Developer Tools Log

No log output observed during these events.

Platform and Versions

• Operating System: Windows 10
• CMake Version: 3.11.0-rc3
• VSCode Version: 1.25.1
• CMake Tools Extension Version: 1.1.0
• Compiler/Toolchain: Visual C++ 2017

Other Notes/Information

This seems to happen most frequently if I switch between branches that have a lot of differences.

[vector-of-bool]

I’m marking this as an upstream bug. CMT doesn’t use cmake-server’s file-watching facilities, so it’s not helpful to the ext. It would be good to be able to disable it if possible, but there isn’t yet an option to do so. I too have seen cmake-server lock up on systems with a huge number of file changes also while running intrusive security software (Webroot in my case, which causes me no end of grief).

[github-actions[bot]]

This issue has been closed automatically because it needs more information and has not had recent activity.