Clangd auto-completion becomes slow #2019
Replies: 2 comments
-
I have tested on many files again, and I found that clangd works fine on some files, while it is very slow on others. In the end, I found that when I define a large array of |
Beta Was this translation helpful? Give feedback.
0 replies
-
I've found the same issue #967 and #1808 sorry for noise! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I utilize clangd for algorithm competitions like Codeforces and AtCoder, where despite having numerous files in my directory, clangd is tasked with providing auto-completion for a single file exclusively, disregarding others. Omitting a
compile_commands.json
file, I anticipate clangd to function in single file mode. This setup had been flawless until last Saturday, consistently furnishing swift auto-completion.However, last Saturday, the pace of clangd's auto-completion inexplicably decelerated. I distinctly recall no modifications made to clangd configurations or version upgrades. Presently, it consumes nearly 1 second to display auto-completion suggestions.
Perusing the logs, I noted prolonged operations:
During the wait for clangd auto-completion, VSCode indicates:
clangd: parsing includes, parsing main file
.Despite updating clangd's version and purging all configurations, the issue persists.
Within VSCode, my clangd configurations are as follows:
I've also experimented by creating a new empty folder for coding, where clangd promptly delivered auto-completions.
However, I prefer not to create a new folder for each coding session. Is there a method to restore clangd's swift auto-completion while operating within my complete code directory?
And this is my full clangd log.
clangd-log.txt
Apologize for my poor English. I'm using ChatGPT to help me with the translation. Thank you for your assistance in advance!
Beta Was this translation helpful? Give feedback.
All reactions