it is stuck when the project is big

[figozhang]

it is stuck when the project is big, for example i open the linux kernel , how to fix it?

[ludovicchabant]

What do you mean by "it is stuck"?

For big projects, ctags will take a long time to complete -- that's just how it is, and outside of Gutentags' reach. However, it shouldn't get anything "stuck", since it's running in a background job?

[redbug312]

I've experienced the similar situation when editing big projects. It seems that ctags causes lots of iowait and freeze the whole operating system rather than just vim itself.

Disabling g:gutentags_generate_on_write might be the solution.

[ghost]

Same issue, vim not responsed and hang up the os on ctags of 3MB when I try to surf through path candidates of completion using asyncomplete & asyncomplete-tags.vim, must force physical reboot the system. gvim 8.1 1-116 / windows10.

[ghost]

Please refer to this issue: https://github.com/prabirshrestha/asyncomplete.vim/issues/75

I'm using Universal Ctags 0.0.0(96d39e43), on windows10

[ludovicchabant]

@RedBug312 Disabling g:gutentags_generate_on_write might not do much since it only runs ctags on the one file that was written. But disabling some of the other ones (generate_on_new and generate_on_missing) could mitigate the problem.

@tuyenpm9 Could ctags somehow block on bad/corrupted files, or files with inaccessible permissions?

[ghost]

The issue from asyncomplete causing io issue somehow, there's workaround solution from refered link I mentioned above. With good .ctags that exlude unnecessary files, I feel it's okay with vim-gutentags.

[ludovicchabant]

Has anybody experienced Gutentags making Vim slow or unresponsive recently? It looks like it might have been caused by a combination of plugins and Vim bugs?

Also, I could imagine that if the background ctags process is spitting out lots of warnings, it might trigger a lot of IO with the Vim process -- if you run with g:gutentags_trace enabled, you would see all those warnings (if any) in your :messages.

[ghost]

I've just do a profiling vim with and without gutentags, combine with other plugins, I don't see any different 000.00X - X is difference compare two cases. Maybe it slow when in actual use instead of loading?

[ActionScripted]

We've recently added a third-party library to our codebase and now if I open NeoVim, edit a file and quit it hangs while things are (re-)generated:

time nvim
# Edited a file, closed. Took ~2s.
nvim  120.61s user 10.39s system 101% cpu 2:09.13 total

Even when files don't change, this keeps happening. I don't think my issue is a fault of Gutentags but wanted to share.

---

ctags via Universal Ctags 5.9.0(p5.9.20210620.0) and vim-gutentags at 1337b1891b9d98d6f4881982f27aa22b02c80084

[cassepipe]

I noticed a slow down but I think the reason is just that I am working of big typescript codebases. Way bigger than my usual C musings. I wonder though, I have set up the option that will have gutentags works only if if it finds a Makefile but it seems to be generating tags no matter what.