macvim-dev / macvim-dev/macvim

How do I debug MacVim crashing?

Open
#1,407 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Vim Script
Stars
7.9k
Forks
691
PR merge metrics
No merged PRs in 30d

Description

Steps to reproduce

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the reported MacVim installation and environment, then compare MacVim.app with the terminal commands and clean-mode runs listed in the issue. Check the macOS diagnostic-report location and capture a crash log or a reproducible configuration; done means identifying a reproducible cause or obtaining actionable crash evidence.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, vim
Domain
desktop
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.