Bug 2210488

Created attachment 1967348 [details]
File: open_fds

Created attachment 1967349 [details]
File: cpuinfo

Created attachment 1967350 [details]
File: mountinfo

Created attachment 1967351 [details]
File: core_backtrace

Created attachment 1967352 [details]
File: os_info

Created attachment 1967353 [details]
File: limits

Created attachment 1967354 [details]
File: proc_pid_status

Created attachment 1967355 [details]
File: backtrace

Created attachment 1967356 [details]
File: environ

Created attachment 1967357 [details]
File: dso_list

Created attachment 1967358 [details]
File: maps

In order to debug this we would need a reproducer with an minimal config file. Please document the steps clearly how to reproduce.

Here is a minimal config file you can modify. Save as repro.lua and run with `nvim -u repro.lua`. Once you have a reproducer create a tarball of the ~/.repro directory:




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

I cannot reliably reproduce it with my usual vimrc nor your setup, this only happened once so far. Any other options to explore?

I can't find any obvious issue in the code.

just shutdown neovim in a saved session


reporter:       libreport-2.17.10
type:           CCpp
reason:         nvim killed by SIGABRT
journald_cursor: s=022f9e51d14a4b938334433092a24785;i=869a0;b=ca1df5887b2e455db979a132d929daa4;m=954c0609;t=5fdfd8f2a60e6;x=80e052425901d678
executable:     /usr/bin/nvim
cmdline:        /usr/bin/nvim --embed
cgroup:         0::/user.slice/user-4211261.slice/user/app.slice/flatpak-session-helper.service
rootdir:        /
uid:            4211261
kernel:         6.3.6-200.fc38.x86_64
package:        neovim-0.9.1-2.fc38
runlevel:       N 5
backtrace_rating: 4
crash_function: uv_close
comment:        just shutdown neovim in a saved session

I was editing files of relatively small sizes in a few different panes in Zellij, and all of a sudden one of the instances crashed.


reporter:       libreport-2.17.11
type:           CCpp
reason:         nvim killed by SIGABRT
journald_cursor: s=011ed7828d954dae82bec55adc7102d0;i=274ab;b=80719f4d74264309b1ae2c66c3849432;m=13bc180fc;t=5ff8ca9799a20;x=32aeaf0acb8fd365
executable:     /usr/bin/nvim
cmdline:        /usr/bin/nvim --embed bootstrap.sh
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-gnome-alacritty-3543.scope
rootdir:        /
uid:            1000
kernel:         6.3.8-200.fc38.x86_64
package:        neovim-0.9.1-2.fc38
runlevel:       N 5
backtrace_rating: 4
crash_function: uv_close
comment:        I was editing files of relatively small sizes in a few different panes in Zellij, and all of a sudden one of the instances crashed.