Memory leak in Codeium

[zyazevav]

Hi, a couple of days ago I found a problem with the fact that the file language_server_windows_x64.exe consumes excessively much RAM and loads the processor for 25-30 processes in idle mode. As soon as I open VS Code, it gradually begins to consume RAM from 20 MB, gradually increasing its consumption. I had 8 GB of RAM and consumption reached 6-7 GB. Today I increased the RAM to 16 GB and the download began to reach 11 GB, and as if the more memory the more it consumes. The CPU load is kept within 25-35%, as well as the RAM load is kept until I close VS Code or disable the extension

[HomlesFish]

I also found this problem when using Codeium on the rider plugin.

[d-afanasiev]

I also have this problem.
Is there a solution to this problem?

[yangthen]

any solution? can not use it, worry boom

[present-g]

Same problem on MacOS

[yangthen]

looks like a problem with the Enable Search in settings, turn it off，it needs to iterate over all files, too long
or, roll back to version 1.6.xx

[zyazevav]

The following is written in the codeium search settings: When first enabled, Codeium will consume about 25% of CPU while it indexes the workspace. This should take < 10 minutes depending on your workspace size, once per workspace. CPU usage will return to normal automatically. In reality, the CPU remains loaded by 25-30 percent until vs code closes or the extension shuts down. In addition, even if the extension simply loads the entire workspace into RAM, the size of the workspace on disk is significantly less than the memory load of the language_server

[HomlesFish]

looks like a problem with the Enable Search in settings, turn it off，it needs to iterate over all files, too long or, roll back to version 1.6.xx
i roll back to version 1.6.39,but a plugin exception was reported.

[Phil1988]

same here ~50GB RAM usage is "a bit too much" for my taste;

After closing VS Code:

CPU load also decreased by 20%.

[0reo]

Memory issues over here as well :( Ubuntu 24.04, 1.95.3

[vkpdeveloper]

It's actually in their language server; it's still not fixed.

[Tiaansu]

Any update to this issue?

[skills-up]

Massive memory consumption by language server on MacOS. VS Code had become unusable even after disabling codeium extension. Finally had to uninstall codeium altogether, and manually delete its language server to use VS Code properly again.

[vkpdeveloper]

Any update on this??