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

core dump with nvim v0.8.3 #597

Closed
2 tasks done
qcmc17 opened this issue Mar 24, 2023 · 13 comments
Closed
2 tasks done

core dump with nvim v0.8.3 #597

qcmc17 opened this issue Mar 24, 2023 · 13 comments
Labels
bug Something isn't working

Comments

@qcmc17
Copy link

qcmc17 commented Mar 24, 2023

Version confirmation

  • Confirm

Following prerequisites

  • Confirm

Neovim version

v0.8.3

Operating system/version

CentOS Linux release 7.9.2009 (Core)

Terminal name/version

default bash

$TERM environment variable

No response

Branch info

main (Default/Latest)

Fetch Preferences

SSH (use_ssh = true)

How to reproduce the issue

just launch nvim, after quit core dump is generated.

this is core dump information:
(gdb) bt
#0 0x00007f477081f7b8 in main_arena () from /lib64/libc.so.6
#1 0x0000000000550deb in multiqueue_put_event (this=0x24e9250, event=...) at /root/neovim/src/nvim/event/multiqueue.c:143
#2 0x00000000005da925 in nlua_schedule (lstate=0x7f4771983380) at /root/neovim/src/nvim/lua/executor.c:337
#3 0x000000000084c4a6 in lj_BC_FUNCC ()
#4 0x000000000084eb06 in gc_call_finalizer (g=0x7f47719833e0, L=L@entry=0x7f4771983380, mo=0x7f47693408d8, o=) at lj_gc.c:520
#5 0x000000000084ec2a in gc_finalize (L=L@entry=0x7f4771983380) at lj_gc.c:567
#6 0x000000000084fe38 in lj_gc_finalize_udata (L=L@entry=0x7f4771983380) at lj_gc.c:574
#7 0x0000000000830f71 in cpfinalize (L=0x7f4771983380, dummy=, ud=) at lj_state.c:271
#8 0x000000000084c89c in lj_vm_cpcall ()
#9 0x0000000000831372 in lua_close (L=0x7f4771983380) at lj_state.c:297
#10 0x00000000005dbd79 in nlua_common_free_all_mem (lstate=0x7f4771983380) at /root/neovim/src/nvim/lua/executor.c:859
#11 0x00000000005dbd19 in nlua_free_all_mem () at /root/neovim/src/nvim/lua/executor.c:837
#12 0x0000000000620581 in free_all_mem () at /root/neovim/src/nvim/memory.c:840
#13 0x00000000005e6fc6 in os_exit (r=1) at /root/neovim/src/nvim/main.c:610
#14 0x00000000005e749f in getout (exitval=0) at /root/neovim/src/nvim/main.c:731
#15 0x000000000056ca53 in ex_quit (eap=0x7ffc91e13ac0) at /root/neovim/src/nvim/ex_docmd.c:4531
#16 0x00000000005658e8 in execute_cmd0 (retv=0x7ffc91e13a78, eap=0x7ffc91e13ac0, errormsg=0x7ffc91e13a90, preview=false) at /root/neovim/src/nvim/ex_docmd.c:1620
#17 0x00000000005674a4 in do_one_cmd (cmdlinep=0x7ffc91e13cd8, flags=0, cstack=0x7ffc91e13e00, fgetline=0x57d31c , cookie=0x0)
at /root/neovim/src/nvim/ex_docmd.c:2275
#18 0x0000000000563563 in do_cmdline (cmdline=0x0, fgetline=0x57d31c , cookie=0x0, flags=0) at /root/neovim/src/nvim/ex_docmd.c:584
#19 0x00000000006467b0 in nv_colon (cap=0x7ffc91e14460) at /root/neovim/src/nvim/normal.c:4058
#20 0x0000000000640313 in normal_execute (state=0x7ffc91e143e0, key=58) at /root/neovim/src/nvim/normal.c:1172
#21 0x000000000071670e in state_enter (s=0x7ffc91e143e0) at /root/neovim/src/nvim/state.c:88
#22 0x000000000063e5a0 in normal_enter (cmdwin=false, noexmode=false) at /root/neovim/src/nvim/normal.c:471
#23 0x00000000005e6f0e in main (argc=1, argv=0x7ffc91e147a8) at /root/neovim/src/nvim/main.c:583

Expected behavior

exit nvim without core dump

Actual behavior

No response

Additional information

No response

@qcmc17 qcmc17 added the bug Something isn't working label Mar 24, 2023
@ayamir
Copy link
Owner

ayamir commented Mar 24, 2023

Does it appear when using nvim --clean? Is it relevant with nvimdots?

@qcmc17
Copy link
Author

qcmc17 commented Mar 24, 2023

nvim --clean

i tried nvim --clean, works fine. maybe some plugins lead this problem

@ayamir
Copy link
Owner

ayamir commented Mar 24, 2023

Do you use nvimdots for root user?

@qcmc17
Copy link
Author

qcmc17 commented Mar 24, 2023

Do you use nvimdots for root user?

right

@Jint-lzxy
Copy link
Collaborator

You only provided stack backtrace for the main thread. What was the cause of this crash?

Can you provide the following extra debugging info (as much as possible):

Code Type (e.g., x86-64):
Parent Process:
Crashed Thread:

Exception Type (e.g., SIGSEGV):
Exception Codes:

Termination Reason:

VM Region Info:
Full Stack Backtrace (All used threads):

@ayamir
Copy link
Owner

ayamir commented Mar 26, 2023

My suggestion is don't use root user to use this config. Maybe some plugins have conflict with root privilege.

@CharlesChiuGit
Copy link
Collaborator

Normally root user can only use default nvim/vim.

@qcmc17
Copy link
Author

qcmc17 commented Apr 3, 2023

My suggestion is don't use root user to use this config. Maybe some plugins have conflict with root privilege.

bad news, i tired build neovim from source with tag v0.8.3 and use nvimdots main branch on ubuntu22.04 for non-root user, but the coredump problems still exists,maybe u can reproducer the issues according to the above description.

@ayamir
Copy link
Owner

ayamir commented Apr 3, 2023

i tired build neovim from source with tag v0.8.3

Have you tried using the deb or Appimage provided by neovim releases?

@CharlesChiuGit
Copy link
Collaborator

CharlesChiuGit commented Apr 3, 2023

Or just decompress the tar.gz file from the neovim repo?

I always use this on ubuntu22.04, never seen this error before.

@qcmc17
Copy link
Author

qcmc17 commented Apr 4, 2023

i tired build neovim from source with tag v0.8.3

Have you tried using the deb or Appimage provided by neovim releases?

i will try deb or Appimage later.

@qcmc17
Copy link
Author

qcmc17 commented Apr 4, 2023

Or just decompress the tar.gz file from the neovim repo?

I always use this on ubuntu22.04, never seen this error before.

thank you, i will try later.

@qcmc17
Copy link
Author

qcmc17 commented Apr 6, 2023

i tired build neovim from source with tag v0.8.3

Have you tried using the deb or Appimage provided by neovim releases?

i tried using the deb package from neovim repository, problem solved.

@qcmc17 qcmc17 closed this as completed Apr 6, 2023
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

4 participants