-
Notifications
You must be signed in to change notification settings - Fork 36
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
Intermittent crashes while scrolling #90
Comments
I have the same issue, seems to happen most often when I am spamming Ctrl-D/U to scroll through my code. No red error messages or anything, just kicks me back to the terminal and I have to start up nvim again. I've disabled the plugin for now and will report if the crashes continue or stop happening. EDIT: The performance fix seen here #80 (comment) still does not fix this crashing issue... |
Have you always experienced this or did this issue appear after a Neovim or Neoscroll update? Is there any way to reproduce it? Unfortunately, I have never experienced this myself. |
I can't say when it started appearing and unfortunately don't know a reliable way to reproduce this. I was hoping there would be logs somewhere that I could look at |
What config are you using? If you see it happening with a particular config, e.g. when using easing functions, it might give us some clues. |
To add a bit of info - I have the same exact behavior as @richardso21, i.e. usually happens when spamming Ctrl-D/U quickly, and especially while LSP is loading (not sure about this one). Regarding my config, I'm pretty sure it's the default one:
|
Yes, spamming those keybinds while the LSP is loading usually spells trouble. This is my config with lazy.nvim (pretty barebones): {
"karb94/neoscroll.nvim",
opts = {
easing_function = "sine",
},
} As for my lsp setup, I am using a combination of lsp-zero, mason, lspconfig, and nvim-cmp. |
I am also having this issue - sometimes crashing with My config is simply: require("neoscroll").setup({
easing_function = "sine",
})
|
Update to this thread, I realize that this issue happens even when I am scrolling with my mouse wheel as well, even with this plugin removed. So if others experience this exact same thing as well, I think this is more of a neovim issue than it is neoscroll... |
I can also add that I have seen this issue after replacing |
Can you pull the latest commit? It adds a |
Haven't pulled the latest commit yet, but on
That's all, and it occurs every time I crash when scrolling ( |
Yes, I am also seeing these messages in my log. And these occurred while using
I am going to switch back to neoscroll and see if the latest commit has fixed the issue. |
@edwardbaeg I'm not sure how the |
I had recently switched over to try |
Since it's also happening with mini.animate, I suppose this is a neovim issue? However, if I run |
After a very long time of investigating which plugin would be causing this (so long in fact that I don't want to admit it), I pinpointed the cause to be messages (especially lsp progress messages) displayed by My fix for this is to set UPDATE: I can't reproduce this issue anymore using neovim nightly, but I encountered more inconvenient unrelated bugs along the way so I'll be staying on stable with this fix for now 😅 |
I don't have |
@edwardbaeg could you please try to reproduce this without any plugins other than nvim-lspconfig? Also pull latest commit as it prevents endless loops (see #95) although this mostly applies to files with wrapped lines. |
@karb94 I have not experienced any similar crashes for the last week. This may have resolved itself. Maybe this was due to some bad interaction with another plugin that was updated recently |
This may have been caused at least in part by neovim/neovim#27859 |
I'll close this for now as it doesn't appear to be related to Neoscroll. |
Sometime, usually upon first loading a file and scrolling (while LSP is loading, I think), neovim silently crashes near the end of the scroll. How do I debug this - where should I look for the logs?
I am on MacOS, using neoscroll with the default config.
The text was updated successfully, but these errors were encountered: