Screen flashes black & other random behavior in Mojave

[aholub]

I don't know how to say it other than the screen goes completely nuts in Mojave. It flashes black when I try to move the cursor, goes entirely black when I type ":", formats in odd ways. seems to jump around in the file. It's just generally bonkers. I fixed it by issuing the following:

defaults write org.vim.MacVim MMUseCGLayerAlways -bool YES

which I don't understand, but got from an earlier post for a similar problem. The attached .zip holds a .mov video screen capture of the problem. All I'm doing is issuing a sequence of j commands, finishing up with a :q .

VIM-bug.mov.zip

[aholub]

Actually, the defaults fix doesn't fully fix the problem. I'm still seeing occasional bad behavior. The last time macvim crashed entirely. I've attached the crash report.

report.txt

[arturoherrero]

I have the same problem. I'm not sure if this issue is the same issue described in #751.

[longcao]

I'm also seeing this on macOS Mojave 10.14.1, installed with Homebrew:

macvim: stable 8.1-151 (bottled), HEAD
GUI for vim, made for macOS
https://github.com/macvim-dev/macvim
Conflicts with:
  vim (because vim and macvim both install vi* binaries)
/usr/local/Cellar/macvim/8.1-151_2 (2,178 files, 34.9MB) *
  Poured from bottle on 2018-12-01 at 09:16:45
From: https://github.com/Homebrew/homebrew-core/blob/master/Formula/macvim.rb
==> Dependencies
Required: cscope ✔, lua ✔, python ✔
==> Requirements
Build: xcode ✔
==> Options
--HEAD
	Install HEAD version

@aholub And for what it's worth, disabling the Core Text renderer and and restarting MacVim as noted in #751 (comment) seems to fix the issue for me for now.

[tkandal]

Hello

After upgrading to latest MacVim on MacOS 10.14.1 with Homebrew, I also have this problem.
Disabling the Core Text renderer as noted in #751 (comment) also fixed my issue.

[arturoherrero]

I also disabled the Use Core Text renderer from the preferences and MacVim seems to be stable but I've lost the typography I use and it looks worse.

[ychin]

This is a duplicate of #751, and PR #757 just fixed this. Closing.

@arturoherrero Just curious though what did you mean by "losing the typography"? You should be able to turn on Core Text renderer again (which is the default supported path) but I'm curious what the issue was in the non-Core Text renderer.

[arturoherrero]

@ychin I'm not sure if you can appreciate with the screenshots.

This is the default preferences:

This is the disabled the Use Core Text renderer, the editor looks worst. The NERDTree separation is not straight and there is slightly more space between the elements.

[ychin]

Ah ok. Yeah that looks about what I would expect. Hope the fix solved the issue for you.

[arturoherrero]

Thanks a lot!