-
Notifications
You must be signed in to change notification settings - Fork 702
The CopilotForXcode used 508GB of memory #298
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Seeing simliar behavior. Was wondering why my machine suddenly wanted to take a trip to the moon. |
The indexing job may consume significant system resources while indexing your workspace. Could you share the approximate size of your codebase so we can better estimate the impact? thanks. |
|
|
@zenangst @akuzminskyi thank you for sharing the info. they're helpful for us to setup benchmark. we will investigate further to see how to mitigate it. |
I also work on a huge project and I'm getting constant |
Hi @akuzminskyi, in your case, the real memory usage is 201M, not 508G. 508G memory in your screenshot is the virtual memory space that’s given to copilot. It has no relation with the actual physical memory and storage usage. I took a look into all nodejs processes running in my MacBook Pro, all of them show 390G+ virtual memory size. I think virtual memory size is not a meaningful metric for evaluating memory consumption. |
@testforstephen thanks. feel free to close the issue if this is irrelevant |
Describe the bug
The CopilotForXcode used 508GB of memory, I suppose this is too much.
Versions
Screenshots

Logs
github-copilot-for-xcode.log.zip
Additional context
The text was updated successfully, but these errors were encountered: