Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

🐛bug: lsp component slows down NeoVim when clients are starting #17

Closed
JeanMertz opened this issue Jan 6, 2025 · 4 comments
Closed
Labels
bug Something isn't working

Comments

@JeanMertz
Copy link

Neovim version (nvim -v)

NVIM v0.11.0-nightly+6dc0eb9

Operating system/version

macOS 15.1

Describe the bug

Given this plugin, and any other plugin that adds "smooth scrolling" (tried both vim-smoothie and neoscroll.nvim), I noticed that having the lsp component enabled significantly slows down rendering (I presume) inside Neovim, and smooth scrolling starts to stutter a lot.

Once the LSP clients are finished loading, scrolling is smooth again.

By trying two different smooth scrolling plugins, and enabling/disabling the lsp component specifically, I am confident the issue lies with this specific component.

I looked at the Wiki page for this component, and (as expected) setting lsp_progress to false solves the issue.

I wonder if it's triggering too many updates or something, but I couldn't find a way to reduce the updating/redrawing frequency?

Steps To Reproduce

n/a

Expected Behavior

n/a

Current Behavior

n/a

Minimal init.lua

No response

More info

No response

@JeanMertz JeanMertz added the bug Something isn't working label Jan 6, 2025
@JeanMertz JeanMertz changed the title 🐛bug: lsp component slows down NeoVim at startup 🐛bug: lsp component slows down NeoVim when clients are starting Jan 6, 2025
@Zeioth
Copy link
Owner

Zeioth commented Jan 8, 2025

Cannot repro. Likely to be a CPU power issue.

Tested with mini.animate.

@JeanMertz
Copy link
Author

Thank you for the reply. I'll report back if mini.animate works as expected.

It is true that – even though my M2 Max with 64GB of RAM is more than capable – given that I have rust-analyzer running at start, it could be pegging all of my cores at 100% for 10–20 seconds as it processes the code. Still, though, as soon as I disable this plugin, there's no slowness to see in the editor.

@Zeioth
Copy link
Owner

Zeioth commented Jan 8, 2025

I don't see anything that could potentially cause slowness in the component or its provider.

I assume mini.animate will fix it, but if not feel free to clone the project and look into the code of the component.

@Zeioth
Copy link
Owner

Zeioth commented Jan 14, 2025

Closing for now, please feel free to re-open if necessary.

@Zeioth Zeioth closed this as completed Jan 14, 2025
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants