When using this plugin ctags spawned processes are taking over 100% cpu
zzantares opened this issue · 7 comments
Whenever I use this plugin, and I'm working with vim, some ctags processes are spawned (like 5 ctags processes) and every one of them are taking up to 80%-100% of CPU usage.
At first I thought it was the patched fork of ctags, so I uninstalled it, and keep exhuberant ctags, but the behaviour is the same.
I'm using Mac OSX 10.10.5 and Vim 7.4. What can I do?
Is this happening with every code base or only on some specific ones?
I've experienced something like this (never ending ctags indexing) but only with my ctags patches on the mkusher/padawan.php project.
If you can pinpoint it to a file or project, can you send me the code in question?
Sorry but seems the problem was not with this plugin, I'm suspecting the problem comes from vim itself, may be the bundled phpcomplete.
I'm still pretty much interested in reproducing this, since I'm the maintainer of the bundled version too, if it's buggy i want to know about it pretty much (-:
Ok, what we can do to see where is the problem because I don't know where the problem is, as soon as I install ctags and use vim, some minutes latter the CPU process are over 80%-100%.
I understand. The plugin itself never calls ctags directly, so I'm not sure what to make of this yet.
Do you have vim-tagbar or some other plugin that would call ctags to regenerate tags when saving files, or generate tags when you are opening one? I would try to disable them (one-by-one) and see if the problem goes away so you can pinpoint it to one of them.
If that isn't it, do this happens even if you don't trigger completion? By default this plugin doesn't do anything until it's called by either with ctrl+x,ctrl+o or by some other plugin like YouCompleteMe, supertab, neocomplete.
You can try to check top or something like that to see if it's the vim process or a ctags process that uses the cpu when it happens too.
I have been working without issues now, I updated to Mac OS X 10.11, I'm pretty sure phpcomplete is not the problem as I was thinking, very well could be "szw/vim-tags" is my principal suspect.
I see, thank you for the followup. I'm gonna close this then.