Skip to content
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

ycmd eats all the memory when editing a python file #1389

Closed
yshui opened this issue Feb 24, 2015 · 4 comments
Closed

ycmd eats all the memory when editing a python file #1389

yshui opened this issue Feb 24, 2015 · 4 comments

Comments

@yshui
Copy link

yshui commented Feb 24, 2015

I was editing a python file and suddenly my system became unresponsive. I managed to run some command to check the memory usage, and in 'top' it shows a python2 process take 110% memory. And I check the command line of that process and find out it's ycmd.

For now, I don't have a way to reproduce this problem.

@vheon
Copy link
Contributor

vheon commented Feb 24, 2015

Are you using tag files? We have a known issue #595 about that, but could be that the file you're editing require Jedi to eat lots of ram to give you candidates, or could be some other leaks entirely that we don't know about (even though I doubt it) but my money is on Jedi. If you could find a way to reproduce this would be great.

@yshui
Copy link
Author

yshui commented Feb 25, 2015

@vheon I don't use tag files. And at the point of system becoming unresponsive, it seems ycm is indeed trying to provide completion candidates. So it is probably Jedi.

I'll try to get more info next time I encounter this problem. It will be helpful if you could tell me how can I gather necessary informations when I see this

@vheon
Copy link
Contributor

vheon commented Feb 25, 2015

@yshui I don't know if there's a way to know if the ram is used by Jedi of by ycmd itself. That is because for the moment Jedi is embedded into ycmd. There was someone that wanted to extract Jedi into its own process (allowing to run Jedi from a python3 completer and get completion for python3), you could see the proposal #1278. If it was in a separate process we could see if the ram was own by jedi or by ycmd.

@Valloric
Copy link
Member

Sounds like a Jedi bug. I recommend creating a small test case using just Jedi and filing upstream.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants