Instantly running out of available memory and freezing on project sync

[Algomorph]

Description of the bug:

All of a sudden with the new plugin (CLion version), I'm instantly running out of memory on a project where the plugin used to work for the past 3 years... There's no change to the project that I believe could have precipitated this... I'm seeing memory usage jump all of a sudden to >20 GB, I don't even have time to "produce memory report" before it freezes. Unfortunately, I cannot share the details of the project, as it is proprietary. I've already tried to completely recreate the project by copy/pasting the older .bazelproject, I'm experiencing the same exact effect after doing so.

Even after I stop the sync mid-way when I see memory go up, it doesn't seem to stop and completely clogs my memory.

Which category does this issue belong to?

No response

What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

I can reproduce it by initiating a project sync or any partial sync.

Which Intellij IDE are you using? Please provide the specific version.

CLion 2025.2.4

What programming languages and tools are you using? Please provide specific versions.

C++, typescript, python

What Bazel plugin version are you using?

2025.11.03.0-api-version-252

Have you found anything relevant by searching the web?

Not so far.

Any other information, logs, or outputs that you want to share?

No response

[Algomorph]

Here's a CLion log file for just before the freeze...
idea.log

[Algomorph]

I've established the reason for the extreme memory usage. The bazel project in question is wrapped inside a CMake project (to make it consumable by other CMake projects), so there were several build directories, such as cmake-build-release, in the project directory, which would contain the bazel cache as well as the cmake cache for an entire build. Even though the .bazelproject was configured as not to resolve targets automatically from all directories, simply because "." was included under directories:, it was trying to inspect the entire tree inside the cmake-build-release.

Previously, this was managable by excluding directories from within .clwb/.blaze/modules/.workspace.im, by using the elements, but somehow this didn't work in this case, i.e. the file kept getting reset automatically by the plugin at runtime, erasing some of those build folder exclusions from .workspace.im -- and these kept getting scanned during project Sync.

Removing the build directories recursively helped in this situation.

A reasonable remedy for this kind of situation is to re-introduce a formal folder exclusion mechanism via right-click context menu -> Mark Directory As -> Excluded, just like it currently works for CMake projects.

[LeFrosch]

Hi, thanks a lot for the detailed report and the investigation. I'll check what we can do in this situation and get back to you.