-
Notifications
You must be signed in to change notification settings - Fork 918
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
bug: full freeze of Neovim on file reload #1581
Comments
This it not a LazyVim issue. Report an issue upstream if that's what's causing it. |
I just ran into the same. It is indeed caused/realted to value of |
It's clearly a bug. |
Can you try to see if Nightly solved this? If so I will change the defaults so that it only is enabled on nightly. @delice0 same for you |
FWIW, I've been experiencing freezes today as well, but I'm not at my computer at the moment. |
This seems to have been fixed in this PR: neovim/neovim#24230 (comment) |
If someone can confirm it works on nightly, then I'll just disable the feature for now on |
@fredrikaverpil are you on 0.9.2 or a recent nightly? |
I'm not sure what "nightly" means in this context, but |
That's not a fix. With nightly I mean on Neovim nightly. So a recent NEovim build. |
0.9.2 |
@folke seems to be working on nightly (commit: |
@jyuan0 and you get freezes on 0.9.2 as well? I can't reproduce it on either at the moment. |
Sorry, I don't have a build of 0.9.2 handy for testing. |
I also experience the same issue and I am on 0.9.2. |
Still the same. I need someone to confirm:
Alternatively if someone can give me steps to reproduce I can test it myself. |
I don't know if this will help, but I can see the issue after I update to the latest version of LazyVim and then restart NeoVim and open a file. I don't see it when the splash screen shows up upon opening, but only when I open a file. Hope that helps. And thanks. |
I just pushed a changed to enable treesitter folding only on 0.10 |
Working again in 0.9.2 Still freezes in 0.10 Specifically when opening telescope symbols |
just tested with a 12000 lines lua file and have no issues |
@folke here's a repro that breaks for me on neovim 0.9.2. repro.lua: -- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")
-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end
-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath })
end
vim.opt.runtimepath:prepend(lazypath)
require("lazy").setup({
spec = {
-- add LazyVim and import its plugins
{ "LazyVim/LazyVim", commit = "3849e0150b0a616dbd6e7e12ec5025aff6c81d39", import = "lazyvim.plugins" },
-- { "LazyVim/LazyVim", commit = "d989ecc943b3240db0be3aa0369b96089cee4b40", import = "lazyvim.plugins" },
-- import any extras modules here
{ import = "lazyvim.plugins.extras.lang.typescript" },
},
}) echo '{}' > test.json
nvim -u repro.lua test.json Then in Lazyvim execute command |
Great, thanks! I can reproduce this on It works correctly on |
Probably not the most useful comment, but I was dealing with this at work today and was just logging on now to report it. Glad to see it is sorted out already. I tested LazyVim 9.0.2 on Neovim 0.9.2 and can also confirm all is well here. :) |
Pro tip: not reporting bugs ensures that they will never be fixed (or the fix backported, in this case). |
Right, didn't think about backporting. Thanks! |
Did you check docs and existing issues?
Neovim version (nvim -v)
0.9.1 & 0.9.2
Operating system/version
Linux & macOS Sonoma
Describe the bug
I've been experiencing what effectively feels like a deadlock on file reloads after updating to the latest version of LazyVim. I'm fairly confident this is due to LazyVim as I am able to consistently reproduce the issue with:
but am not able to reproduce the issue when I use the immediate previous commit
364bcf325d91a06e6bd6516bdfed84399566cdb6
.I've been trying to get a sense of what exactly is triggering this deadlock-like behavior, but haven't had much luck. The farthest I've gotten is using:
which spits out a file dominated by the following callstack:
I do see a comment about infinite recursion here: https://github.com/neovim/neovim/blob/1e7e9ee91f73c62b8c5ba9dbdabba3a3b6dc0130/runtime/lua/vim/treesitter/_fold.lua#L280
not sure if this is related?
Steps To Reproduce
cargo fmt
in a separate tmux pane).kill -9
.Expected Behavior
Neovim should not freeze.
The text was updated successfully, but these errors were encountered: