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

bug: Segmentation fault when use ( neovim + lazyvim) on Windows msys2. #1862

Open
4 tasks done
KyleDeng opened this issue Dec 23, 2024 · 5 comments
Open
4 tasks done
Labels
bug Something isn't working

Comments

@KyleDeng
Copy link

Did you check docs and existing issues?

  • I have read all the lazy.nvim docs
  • I have updated the plugin to the latest version before submitting this issue
  • I have searched the existing issues of lazy.nvim
  • I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

v0.10.2 (LuaJIT 2.1.1734355927)

Operating system/version

Windows11

Describe the bug

In Windows11, install msys2 and in mingw64 install neovim.
Just by using neovim, you can run the program correctly.
If lazyvim is installed, neovim reports a "Segmentation fault" or causes the terminal to stop running.

Steps To Reproduce

  1. Install msys2
  2. pacman -S mingw-w64-x86_64-neovim --noconfirm
  3. git clone https://github.com/LazyVim/starter C:/Users/$USER/AppData/Local/nvim
  4. nvim ~/.bashrc

Expected Behavior

neovim reports a "Segmentation fault" or causes the terminal to stop running.

Repro

No response

@KyleDeng KyleDeng added the bug Something isn't working label Dec 23, 2024
@KyleDeng
Copy link
Author

msys2 version is "msys2-x86_64-20241208"

@max397574
Copy link
Contributor

why would this be related to lazy.nvim?
if anything it comes from lazyvim

but neovim should never segfault at all so it's likely an upstream issue

@KyleDeng
Copy link
Author

#1321

This is the problem that other people have, we have the same problem,
Yes, the upgrade version can solve the problem,
My neovim has been upgraded, but the problem still exists.

@ienapliss
Copy link

ienapliss commented Dec 24, 2024

Hi, I'm the one who wrote about #1321, which resolved itself.

I can no longer reproduce the issue.
I upgraded my Neovim package to the latest version (mingw-w64-x86_64-neovim-0.10.3-1 from 0.10.2-2) and found that it works just fine.

The previous issue was 100% reproducible using the minimal config, and as explained, it was triggered only when using Neovim mingw package in combination with lazy.nvim.

@KyleDeng
Copy link
Author

Hi, I'm the one who wrote about #1321, which resolved itself.嗨,我是写 #1321 的人,它自行解决了。

I can no longer reproduce the issue.我无法再重现该问题。 I upgraded my Neovim package to the latest version (mingw-w64-x86_64-neovim-0.10.3-1 from 0.10.2-2) and found that it works just fine.我将我的 Neovim 软件包升级到最新版本(从 0.10.2-2 到 mingw-w64-x86_64-neovim-0.10.3-1),发现它工作得很好。

The previous issue was 100% reproducible using the minimal config, and as explained, it was triggered only when using Neovim mingw package in combination with lazy.nvim.使用最小配置,上一个问题是 100% 可重现的,如前所述,只有在将 Neovim mingw 包与 lazy.nvim 结合使用时才会触发。

Yeah, I'm in the same situation,
neovim alone is fine, but lazyvim will crash when configured.
(git clone https://github.com/LazyVim/starter C:/Users/$USER/AppData/Local/nvim)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants