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

No LSP in a project and memory leak #2623

Open
SuperJura opened this issue Jul 27, 2024 · 2 comments
Open

No LSP in a project and memory leak #2623

SuperJura opened this issue Jul 27, 2024 · 2 comments

Comments

@SuperJura
Copy link

SuperJura commented Jul 27, 2024

Hello,
I am running neovim 0.9.4 with latest omnisharp-roslyn on windows. I installed this using Mason.

I have a 2-in-1 report and I need some help finding the issue.
In a new project, LSP works normally and I have no problem with memory issue.
When openning a big project I can't get LSP to work. I tried multiple solutions and only moving to https://github.com/razzmatazz/csharp-language-server works, but it has it's own flaws.
The project has 510000+ lines of c# code and more than 2000 cs files. It has one sln file and alot of csproj files.

When I :LSPInfo, I get 0 client(s) attached to this buffer Other clients that match the filetype: cs
and most importantly (I think) root directory: Not found.

in :LspLog I only see a bunch of OmniSharp.Extensions.LanguageServer.Server.LspServerOutputFilter: Tried to send request or notification before initialization was completed and will be sent later OutgoingNotification

How can I start debugging this problem?

Second thing is memory leak, when I leave it running, memory fills up and I have to kill nvim (although I have no LSP)
image

Additionally, when I run the same project in VSCode it works flawlessly without stuttering or memory problems.

@SuperJura SuperJura closed this as not planned Won't fix, can't repro, duplicate, stale Jul 27, 2024
@SuperJura SuperJura reopened this Jul 28, 2024
@nagaohiroki
Copy link

I had the same problem.
I think it's the same issue as #2574.

@SuperJura
Copy link
Author

I tried multiple versions with different options, with no progress.

I will leave this issue open for future references, but I have moved to roslyn.nvim for now.
It's VSCode's lsp so it could be better, but I have to test it more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants