DragonFlyBSD

i guess i can second this one. I'm also running neovim with number of plugins, and I'm experiencing hard lockups when syntax suggest is finding suggestions, should be like when a number of subprocesses are created and destroyed rapidly.

Hello, Matt, thank you very much for the quick response. How is the patch
to be applied? Is it against some branch or does it have to be applied
manually? In the latter case, would that be enough:

cd /usr/src
patch -p1 < vm39.patch
make buildkernel
cp -Rp /boot/kernel /boot/kernel.old
make installkernel
reboot

Is rebuilding the kernel enough or do I have to rebuild world as well?

Best regards,
Martin

Am Di., 6. Mai 2025 um 07:28 Uhr schrieb <
bugtracker-admin@leaf.dragonflybsd.org>:

Issue #3381 has been updated by dillon.

File vm39.patch added
Assignee set to dillon

Please try this patch. I think its a coding bug where we were trying to
compare a field from the 'next' vm_map_entry but during the cut'n'paste
from the previous section that was comparing 'prev' ... I must have
forgotten to change 'prev' to 'next'.

-Matt

----------------------------------------
Bug #3381: System crash while editing with neovim
http://bugs.dragonflybsd.org/issues/3381#change-14588

• Author: marto
• Status: New
• Priority: Normal
• Assignee: dillon
• Target version: 6.6
• Start date: 2025-05-05
  ----------------------------------------
  Hello, I am running DragonFlyBSD with the following specs:
  "uname -a
  DragonFly dragonfly 6.4-RELEASE DragonFly v6.4.1-RELEASE #9: Thu May 1
  08:43:02 EEST 2025 root@dragonfly:/usr/obj/usr/src/sys/X86_64_GENERIC
  x86_64
  "
  I occasionally experience crashes while editing files with neovim in the
  XFCE terminal. The same crash happens also with the nvim-gtk editor. So far
  I wasn't able to reproduce the crash with nvim-qt6. I am using the LazyVim
  distribution as an IDE. The crash report is attached.

Best regards,
Martin

---Files--------------------------------
core.txt.9.tar.bz2 (205 KB)
vm39.patch (598 Bytes)

--
You have received this notification because you have either subscribed to
it, or are involved in it.
To change your notification preferences, please click here:
http://bugs.dragonflybsd.org/my/account

Applying the source patch and rebuilding the kernel should be enough. You installed the 6.4 release branch so you want to be on that branch for now. It would probably work just fine on master too.

Once you are able to test it, if it fixes the problem I will push it to both release and master.

Also note that you don't want to manually cp -Rp /boot/kernel to /boot/kernel.old ... you might run out of space on /boot because that's a full debug kernel. The installkernel target will automatically copy a stripped kernel and modules to /boot/kernel.old before installing the new /boot/kernel.

marto wrote in #note-3:

Hello, Matt, thank you very much for the quick response. How is the patch
to be applied? Is it against some branch or does it have to be applied
manually? In the latter case, would that be enough:

cd /usr/src
patch -p1 < vm39.patch
make buildkernel
cp -Rp /boot/kernel /boot/kernel.old
make installkernel
reboot

I suggest to use nativekernel, which doesn't require to do buildworld first, so it's:

cd /usr/src
patch -p1 < vm39.patch
make nativekernel
make installkernel
reboot

make installkernel will auto backup the old kernel in /boot/kernel.old.

See also the build(7) man page for the nativekernel.

Is rebuilding the kernel enough or do I have to rebuild world as well?

Only need to build and install the kernel, and finally reboot to test it out.
No need to update the world and packages.

Hello,
thank you all for your helpfulness. I was using nvim as an IDE extensively
these days and I never experienced a crash. So, I would assume the bug is
fixed now.

I noticed that the bugfix is already included in 6.4.2, which is great.

Thank you very much again!

Best regards,
Martin

Am Di., 6. Mai 2025 um 10:24 Uhr schrieb <
bugtracker-admin@leaf.dragonflybsd.org>:

Issue #3381 has been updated by liweitianux.

marto wrote in #note-3:

Hello, Matt, thank you very much for the quick response. How is the patch
to be applied? Is it against some branch or does it have to be applied
manually? In the latter case, would that be enough:

cd /usr/src
patch -p1 < vm39.patch
make buildkernel
cp -Rp /boot/kernel /boot/kernel.old
make installkernel
reboot

I suggest to use nativekernel, which doesn't require to do buildworld
first, so it's:

> cd /usr/src
> patch -p1 < vm39.patch
> make nativekernel
> make installkernel
> reboot
> 

make installkernel will auto backup the old kernel in /boot/kernel.old
.

See also the build(7) man page for the nativekernel.

Is rebuilding the kernel enough or do I have to rebuild world as well?

Only need to build and install the kernel, and finally reboot to test it
out.
No need to update the world and packages.

----------------------------------------
Bug #3381: System crash while editing with neovim
http://bugs.dragonflybsd.org/issues/3381#change-14592

• Author: marto
• Status: New
• Priority: Normal
• Assignee: dillon
• Target version: 6.6
• Start date: 2025-05-05
  ----------------------------------------
  Hello, I am running DragonFlyBSD with the following specs:
  "uname -a
  DragonFly dragonfly 6.4-RELEASE DragonFly v6.4.1-RELEASE #9: Thu May 1
  08:43:02 EEST 2025 root@dragonfly:/usr/obj/usr/src/sys/X86_64_GENERIC
  x86_64
  "
  I occasionally experience crashes while editing files with neovim in the
  XFCE terminal. The same crash happens also with the nvim-gtk editor. So far
  I wasn't able to reproduce the crash with nvim-qt6. I am using the LazyVim
  distribution as an IDE. The crash report is attached.

Best regards,
Martin

---Files--------------------------------
core.txt.9.tar.bz2 (205 KB)
vm39.patch (598 Bytes)

--
You have received this notification because you have either subscribed to
it, or are involved in it.
To change your notification preferences, please click here:
http://bugs.dragonflybsd.org/my/account