search

Exafunction / codeium

Other
200 stars 9 forks source link

Memory leak in Codeium #63

Open zyazevav opened 3 weeks ago

zyazevav commented 3 weeks ago

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 Annotation 2024-06-05 160700 Annotation 2024-06-05 160531

HomlesFish commented 2 weeks ago

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

d-afanasiev commented 2 weeks ago

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

pecopeco commented 1 week ago

any solution? can not use it, worry boom

present-g commented 1 week ago

Same problem on MacOS

pecopeco commented 1 week ago

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 commented 1 week ago

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 commented 1 week ago

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.