You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I will be using macvim and maybe once every 2 days it will crash after hours and hours of use. Because of this time lag it's very difficult to run it in --clean mode, or to systematically eliminate plugins as sources of error.
Is there a crash log somewhere?
I looked in ~/Logs/... diagnostic reports (cant remember exact path) and there is nothing there
Expected behaviour
No crashing
Version of Vim and architecture
Latest MacVim
Environment
Latest iTerm, latest OSX, latest macvim, M2 CPU macbook pro
How MacVim was installed
brew install macvim
Logs and stack traces
Trying to learn how to even get this
Vim configuration where issue is reproducable
No response
Issue has been tested with given configuration
by running MacVim.app from GUI macOS interface
by running vim/gvim/etc installed by MacVim
by running other versions of vim (e.g. /usr/bin/vim)
Issue has been tested with no configuration
by running mvim --clean (or gvim, supplied by MacVim distribution)
by running vim --clean (in terminal, supplied by MacVim distribution)
by running vim --clean (in terminal, other suppliers, e.g. /usr/bin/vim)
Other conditions
The both Homebrew packages "vim" and "macvim" are installed
Just to clarify, is individual Vim windows crashing, or the entire MacVim app? For individual Vim, you will see the Vim window suddenly closing, but MacVim would remain open. For MacVim app crashing you should see the entire app crash.
I have really wanted to add better crash detection and throw up a dialog box informing you that Vim has crashed but never got around to doing that. Right now, when a particular Vim window has crashed, we just close it which leads to a rather jarring result unfortunately.
The logs should be located at ~/Library/Logs/DiagnosticReports. You can also use Console.app and then navigate to "Crash Reports" and then filter by "macvim".
This has worked perfectly for almost 10 years, but it just started crashing within the last few months, probably within 3 months, so some update in macvim started it.
When it crashes, the entire mvim window will 100% disappear. When I re-open the entire macvim app. Then go through the swp file restore process.
Heres whats in DiagnosticReports. Theres no other files except these siri ones
When I open Console.app, I went through this before and there's nothing here:
I don't know if it helps but im like... 70% sure its when i activate FZF with control+P. I type so fast and on autopilot i always forget the exact thing that i did to trigger it. obviously you couldnt debug from that small piece of info but i was thinking maybe crash logs for that might be stored in a different place or something
When you say you are running "latest MacVim" in the issue, which version exactly do you mean? It's always useful to provide more info than less if you think there's a regression. There are different ways to install MacVim, after all (binary release vs Homebrew vs building from source), and you can opt in to pre-release builds. You can tell by going to MacVim -> About MacVim.
Sorry, I didn't give as much info because I didnt actually have any useful other debugging information to add to my ticket so I figured it was mostly a wash (mostly was trying to figure out where to even find that 'other info'). Here is some info to help:
Hmm, did you have a crash recently? If there was a crash recently it's supposed to show up in the locations I pointed out but I think they do get cleared after a while. It's also a little suspicious that your "Crash Reports" in Console.app is completely empty. Are you filtering that list or something?
Otherwise you can just go to Console.app and go to the main tab (under Devices), and then hit record, then trigger the crash (if it's reproducible).
Did you also update FZF or Ctrl-P? ARe there more info on when the crash would occur? I do know Vim could crash under some circumstances in the current build (fixed in source but not released yet) but you should still get a crash log.
Yes I believe it crashed today. Let me look again, but I am sure I'm not filtering it. I also clicked around there for some time because I thought it was odd it was blank. The search box is empty. everything on that entire area is grayed out because theres no results. if i click in search box at top right... type, enter, hit escape, it simply doesnt do anything as there are no results.
Next time it crashes I'll try to open it immediately and see if it shows up.
I wish it were easily reproduceable as I could definitely have more info. I tried for a good 30 minutes to make it happen and could not. It does happen mostly once per day or every other day, so thats really my only course of action.
Hmmm... so FZF is up to date, and i regularly update plugins with :plug Upgrade, :plug Update
I wish I had more information... I suppose my best bet is for it to happen again and quick check crash reports.
Activity
ychin commentedon Jun 6, 2023
Just to clarify, is individual Vim windows crashing, or the entire MacVim app? For individual Vim, you will see the Vim window suddenly closing, but MacVim would remain open. For MacVim app crashing you should see the entire app crash.
I have really wanted to add better crash detection and throw up a dialog box informing you that Vim has crashed but never got around to doing that. Right now, when a particular Vim window has crashed, we just close it which leads to a rather jarring result unfortunately.
The logs should be located at
~/Library/Logs/DiagnosticReports. You can also use Console.app and then navigate to "Crash Reports" and then filter by "macvim".Let me know if that works.
9mm commentedon Jun 6, 2023
Its the entire macvim app. Essentially I will open mvim from iterm by pressing
vwhich I use to load the current folder, using this bash script.~/.zsh/bin/vThis has worked perfectly for almost 10 years, but it just started crashing within the last few months, probably within 3 months, so some update in macvim started it.
When it crashes, the entire mvim window will 100% disappear. When I re-open the entire macvim app. Then go through the swp file restore process.
Heres whats in DiagnosticReports. Theres no other files except these siri ones
When I open Console.app, I went through this before and there's nothing here:
Any other ideas? :/
9mm commentedon Jun 6, 2023
I don't know if it helps but im like... 70% sure its when i activate FZF with control+P. I type so fast and on autopilot i always forget the exact thing that i did to trigger it. obviously you couldnt debug from that small piece of info but i was thinking maybe crash logs for that might be stored in a different place or something
ychin commentedon Jun 6, 2023
When you say you are running "latest MacVim" in the issue, which version exactly do you mean? It's always useful to provide more info than less if you think there's a regression. There are different ways to install MacVim, after all (binary release vs Homebrew vs building from source), and you can opt in to pre-release builds. You can tell by going to MacVim -> About MacVim.
9mm commentedon Jun 6, 2023
Sorry, I didn't give as much info because I didnt actually have any useful other debugging information to add to my ticket so I figured it was mostly a wash (mostly was trying to figure out where to even find that 'other info'). Here is some info to help:
Build 3.5.0beta10I installed it via homebrew
brew install macvimychin commentedon Jun 6, 2023
Hmm, did you have a crash recently? If there was a crash recently it's supposed to show up in the locations I pointed out but I think they do get cleared after a while. It's also a little suspicious that your "Crash Reports" in Console.app is completely empty. Are you filtering that list or something?
Otherwise you can just go to Console.app and go to the main tab (under Devices), and then hit record, then trigger the crash (if it's reproducible).
Did you also update FZF or Ctrl-P? ARe there more info on when the crash would occur? I do know Vim could crash under some circumstances in the current build (fixed in source but not released yet) but you should still get a crash log.
9mm commentedon Jun 6, 2023
Yes I believe it crashed today. Let me look again, but I am sure I'm not filtering it. I also clicked around there for some time because I thought it was odd it was blank. The search box is empty. everything on that entire area is grayed out because theres no results. if i click in search box at top right... type, enter, hit escape, it simply doesnt do anything as there are no results.
Next time it crashes I'll try to open it immediately and see if it shows up.
I wish it were easily reproduceable as I could definitely have more info. I tried for a good 30 minutes to make it happen and could not. It does happen mostly once per day or every other day, so thats really my only course of action.
Hmmm... so FZF is up to date, and i regularly update plugins with :plug Upgrade, :plug Update
I wish I had more information... I suppose my best bet is for it to happen again and quick check crash reports.