Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

fvim crashes every time when I click the close button on the top right corner

See original GitHub issue

I start fvim by double click fvim.exe. When I close its window by clicking the x button on top right, it immediately crashes with following stack trace (I am not sure how to copy these text, so have to take a snapshot instead):

Issue Analytics

State:
Created 3 years ago
Comments:16 (10 by maintainers)

Top GitHub Comments

1reaction

jdhaocommented, Oct 26, 2020

fvim release should be v0.2.273-g41ce0c6, before the latest release (which is 4 days ago). I started fvim by double click, it is using my nvim config for Windows. I haven’t tried a clean start without any config.

I will try to reproduce without any config.

0reactions

yatlicommented, Nov 23, 2020

okay, let’s close this for now. I’ve been working on better error reporting/startup sequence so this may get accidentally fixed…

Top Results From Across the Web

Crash when non-current WinBar click closes window #4337

Vim crashes (sometimes) with SEGV when clicking a WinBar in a non-current window and the menu command closes the current window.

neovim/vim crashing macOS if i close the terminal

processes neovim (2) is running", and if i select "close" my system hard crashes. display stops updating, trackpad doesn't do the lil vibration ......

Terminal.app keeps crashing while using VIM

I can tell you that Sierra's Applications -> Utilities -> Terminal works just fine using /usr/bin/vim. Try removing (or saving somewhere ...

vim 100% CPU usage after closing xterm with 'vim file' opend.

Do not exit from vim but close the window with the close button on the right top side of the window. Open another...

Vim crashes whenever I try to quit

I am using the alacritty terminal, and I have tried using CTRL+Q, from this answer, because I thought I hit CTRL+S by accident....