neovide: Crashes on Windows 10

Describe the bug Neovide crashes after opening an empty buffer and typing something.

Also try to open a file (about 200 lines), type or scroll the buffer via the mouse wheel. Crashes as well.

To Reproduce Steps to reproduce the behavior:

  1. Run neovide --log -- --clean in PowerShell
  2. Type something
  3. Neovide freezes 1 or 2 seconds
  4. Neovide crashes (window closed)

Expected behavior Don’t crash.

Screenshots I captured a video (1.84MB in .mp4) of the whole process but, seems unable to upload.

Desktop:

  • OS: Windows 10 22H2
  • Neovide Version: build from 3e575fcd (via cargo install --path .)
  • Neovim Version: 0.9.5 (via scoop install neovim)

Please run neovide --log and paste the contents of the .log file created in the current directory here:

neovide_rCURRENT.log

Additional context This may be a stupid issue. I tried various versions of both Neovide and Neovim, and always crashed. I just have no idea what happened. Could anyone help me out?

Thank you for making this impressed project!

About this issue

  • Original URL
  • State: open
  • Created 5 months ago
  • Comments: 26 (15 by maintainers)

Most upvoted comments

If this was a bug in rust you’d think this would happen a lot more to many more people. There seems to maybe be something specific to your system.

Yes, I agree with you. I will test it on another Windows later.

Not necessarily, there’s a long history of problems related to the code in question.

On January 24th 2021 this was reported, with code demonstrating that read was broken. And as far as I can see that has always been the case before that

That was only fixed one year later on April 26th 2022:

This was detected as a regression on July 5th 2022. But it was not really a regression, it was just an inmproper fix

That was quickly fixed on July 10th:

But, I’m not the only one thinking that the fix is wrong https://github.com/rust-lang/rust/pull/98950#pullrequestreview-1030831527. And that is still the code used today.

My point here is that things around this have been broken for a long time, and not affecting many people, or these issues would not stay open for this long.

I will try to create a stress test for the pipe IO, and see if we can get an easier way to reproduce these issues, and potentially report upstream.