Zoom is crashing MacVim :(

[joereddington]

This is a duplicate of this SE question

If I open Macvim, everything works fine, unless I zoom in (using Cmd+"+").

If I do that, then I get a strange black boarder around the added bit of the window and the whole thing freezes.

This is what I see:

(except, bizarrely, it isn't, because I see a black boarder, the mac screenshot shows a light gray one, and the image uploaded to Github mysteriously makes it white, which suggests there's something wrong with me)

...and there is a 40 second video of the problem here: https://youtu.be/cjKWRGLSWTk, which, thankfully, shows the same black border I see. Thank you YouTube.

This appears to be part of a few linked bugs on MacVim, I have quite a lot of trouble with the display not refreshing if I've changed the zoom level while the app is already full-screen and that's quite frustrating.

What information can I give to help you replicate this?

[ychin]

Can you generate some info following https://github.com/macvim-dev/macvim/wiki/Reporting-an-Issue ?

In particular, the most important information is:

1. OS version
2. Whether you have custom vimrc or not (you can try launching MacVim with mvim -u NONE -U NONE
3. Whether you have custom MacVim preferences defaults read org.vim.MacVim | grep 'MM\|SU'.

[joereddington]

Ha! My bad, should have read the wiki.

1. High Sierra 10.13.6
2. /Applications/MacVim.app/Contents/bin/mvim -u NONE -U NONE gives me the same error. And my custom vimrc is here: https://github.com/joereddington/dotvimdirectory (thank you for the reminder to commit and push

Josephs-Mini:.vim josephreddington$ defaults read org.vim.MacVim | grep 'MM\|SU'.
    MMAutosaveColumns = 155;
    MMAutosaveRows = 61;
    MMCurrentPreferencePane = General;
    MMLastWindowClosedBehavior = 2;
    MMOpenInCurrentWindow = 1;
    MMTopLeftPoint = "{375, 980}";
    MMUseCGLayerAlways = 1;
    SUEnableAutomaticChecks = 0;
    SUHasLaunchedBefore = 1;
    SUSendProfileInfo = 0;
Josephs-Mini:.vim josephreddington$ 

Does that help? And answers of the form "Maybe time to upgrade OSX" are probably right on the money...

[eirnym]

To narrow the search of the source of the issue and limit testing various OS X versions, it works fine on 10.14.

[joereddington]

I've updated OS, and it's removed the issue. :(

[ychin]

Sorry for the slow response here. It's nice that you have updated the OS and fixed the issue, but we still need to fix the issue. If other 10.13 users want to chime in please do! Otherwise I may have to hunt down some 10.13 machines / VMs to debug.

[eirnym]

@ychin could you add few labels to show off affected OSes and what the problem is about? We don't have long list of it and It would be much easier to navigate