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: Lazy makes neovim crash (using MSYS MinGW on Windows). #1321

Closed
3 tasks done
ienapliss opened this issue Feb 12, 2024 · 2 comments
Closed
3 tasks done

bug: Lazy makes neovim crash (using MSYS MinGW on Windows). #1321

ienapliss opened this issue Feb 12, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@ienapliss
Copy link

Did you check docs and existing issues?

  • I have read all the lazy.nvim docs
  • 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)

NVIM v0.9.5 Build type: Release LuaJIT 2.1.1707061634

Operating system/version

Windows 11

Describe the bug

I use neovim from MSYS2 MinGW. It always worked fine until some recent updates.
Using Lazy with MinGW packages will make neovim crash.
What's more puzzling: using the same version of neovim from the https://github.com/neovim/neovim/releases (nvim-win64.zip) works just fine...

Sometime I get some more information beside "Segmentation Fault":

  0 [main] git (17340) child_copy: cygheap read copy failed, 0x800000000..0x80000C500, done 0, windows pid 17340, Win32 error 299
  0 [main] git (18376) child_copy: cygheap read copy failed, 0x800000000..0x80000C500, done 0, windows pid 18376, Win32 error 299
389 [main] git 1908 child_copy: dll data read copy failed, 0x180224000..0x180231010, done 0, windows pid 17340, Win32 error 299
578 [main] git 1908 C:\dev\msys64\usr\bin\git.exe: *** fatal error in forked process - couldn't create signal pipe, Win32 error 5
413 [main] git 1909 child_copy: dll data read copy failed, 0x180224000..0x180231010, done 0, windows pid 18376, Win32 error 299
599 [main] git 1909 C:\dev\msys64\usr\bin\git.exe: *** fatal error in forked process - couldn't create signal pipe, Win32 error 5

Steps To Reproduce

  1. Install MSYS2 from www.msys2.org.
  2. Launch mingw64.exe
  3. Install nvim and dependencies
    pacman -S --needed git mingw-w64-x86_64-neovim
  4. Use Lazy (use repro.lua below unchanged)
  5. Launch nvim with: nvim -u repro.lua

Expected Behavior

No Seg Fault

Repro

-- 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)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here
@ienapliss ienapliss added the bug Something isn't working label Feb 12, 2024
@ienapliss ienapliss changed the title bug: Lazy make neovim crash when using MSYS MinGW on Windows. bug: Lazy makes neovim crash (using MSYS MinGW on Windows). Feb 12, 2024
@ienapliss
Copy link
Author

Closing this because apparently the issue is gone after updating the neovim package from mingw.

@KyleDeng
Copy link

Closing this because apparently the issue is gone after updating the neovim package from mingw.

The upgrade did not solve the problem
#1862

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

2 participants