Any way to bug report a clangd memory leak?

I’m trying to use Emacs and lsp-mode, and clangd takes 20+ GB and then macOS starts asking me to shutdown programs. Is there anything I can do to it, to get more specific info on where the bug is so I can file a report?

Did you ever resolve this?

If so,what was the resolution?

Which version of clangd were you running (There is a bug report for clangd-12 which I believe has been resolved).

I’m having the same problem as you on clangd-18

No, I haven’t been using clangd as much recently. I’ve been trying to use my Windows laptop and Visual Studio instead. Unfortunately I have an obsession with using C++ modules, and the VS support there is very bad, so overall my editing productivity is barely better than it was with Emacs and clangd. However at least it does not run amok and take 20GB of RAM.

Turns out there was a bug in clang and hence in clangd Clang runs OOM when checking for constant initialization of array · Issue #51054 · llvm/llvm-project · GitHub that one has been fixed…

But I hit a matching one with unions which is why I was looking at your post since it matched my symptoms.