Terminal.app crashing: Can I disable callbacks?

FYI all, here is the latest feedback (today) on my support case from Apple:

The issue is currently being investigated and data

that you submitted is going to be helpful in providing a solution to the

issue. There is no current workaround or timeframe for a fix, but I will be

following this issue for any updates. We can expect to see a solution come

in the form of a software update so I ask that you keep your computer up to

date and if notice any changes or additional concerns to this issue that you

please let me know, so that I can inform our programmers.

My interpretation of that is we will hopefully see a fix in an upcoming Sierra update, but hard to say when.

Thanks again to all here for the discussions and detective work leading to the crash recipe that Apple is presumably now focused on with their debugging!

I just tested this script in the latest (3rd release) beta for 10.12.3 and it still crashes. I now have a spare Air on which I can test this as soon as betas come out. Obviously it will take some bit of time for these reports to Apple to make it into a fix. Hopefully this is sooner than later. I plan on testing this as soon as betas are bumped and released going forward.

Adding azric47 as a "me too". Seeing this on Mac-Mini and MacBookPro with Sierra 10.12.2; living with it for now, but may look at pulling in vim 8 or El Capitan Terminal or iterm2 if it gets too annoying... 3 crashes on the MBP and 5 (IIRC) on the mini.

I am seeing this issue on MacBook Pro. Crashed many times in the last hour running vim in Terminal while using ssh. I updated to latest vim from Homebrew, and still saw the problem. The new vim reports itself as version 8.0. I did not build from source. macOS version is 10.12.2.

Possibly Terminal is crashing more frequently recently because I've been running vim on files with very long lines.

I need this setup to get my work done. For now I guess I'll switch to iTerm2.

I'm glad I'm not the only one with the problem. Thanks to all.

Just chiming in to say I'm also having the same issue. Working on a text file with long-ish lines in vim (over ssh), I can reliably crash the Terminal app by trying to delete back to the start of the line (d-Home)

Hi,

I'm having the same kind of problem, on a 2016 macbook running mac os Sierra. Vim crashes terminal, and it's related to line sizes.

The script provided above does produce a crash.

Hope this will be resolved quickly, because I use vim a lot, and these crashes are really slowing me down.

bap_clic wrote:

Hi,

Hope this will be resolved quickly, because I use vim a lot, and these crashes are really slowing me down.

Use another app if you have work to do. iTerm & others have been mentioned here.

Hi all,

Given the recent 10.12.3 release that fails to fix the problem, I pinged my Apple support case POC again yesterday. The reply to my query as to exactly what progress Apple has made, if any:

I cannot give you specifics on the issue but I can tell you that we have

received multiple reports of the issue which have been escalated to our

engineering team. We have to wait for them to research the issue, design a

solution and make it available to the public.

Hard to tell from this if they've done anything other than let the bug reports pile up. Maybe, and maybe not.

I continue to encourage all of you fellow sufferers out there who have AppleCare or any other support contract to file your own bug reports, cross-referencing at least the original caseID #100085116387 that John Henning created on 12/8/16. (John, have you had any contact of interest on that case?)

I could make the problem (ViM crashing) go away by removing the "wrapmargin" (or "wm") setting from .vimrc.

Of course, the question then remains why this setting, that I've used for ages together with the "textwidth" setting, causes Terminal to crash in macOS Sierra...

Adding a "me too" so I can follow this thread. I only recently upgraded to Sierra on just one machine where my Mac is little more than a dumb terminal to my Linux servers. What could possibly go wrong? Then my Terminal windows mysteriously go away. I guess I'm afflicted by the same bug. I will start testing it once I don't have these long-running scripts to worry about.

Let me make things clear.

The crash happens *not in vim*, but in Terminal.app itself.

You can confirm this by following steps:

1. Open a Terminal.app window

2. Invoke `/usr/bin/screen`

3. In the screen session, invoke `/usr/bin/vim`

4. Use the reproducer to make a crash happen

5. Open another(new) terminal window

6. Invoke `/usr/bin/screen -r` to reattach to the last (detached by the crash) session

7. Vim is there running happily

Plus 1 for this problem. My situation:

Macbook Pro Early 2011

Fresh install of Sierra went straight to 10.12.2

Data migration from my El Cap time machine backup.

Immediately saw the problem, and it's still there with 10.12.3

I don't use vim very much locally. Like others on this thread, I ssh (over VPN) and use a remote vi (vim 7.3.2035 running on Solaris 11.3 x86). I haven't looked back through my stack traces to compare them in detail, but the traces posted here are very familiar. I can go extended periods of time without Terminal.app crashing, but heavy vi usage does trigger the behavior.

I haven't seen bash command line editing (or command output for that matter) cause the problem. Like others with automatic fingers, I don't know exactly what causes it, but my observation is that it is related to editing long lines (i.e. ones that wrap around the 80 character terminal width I use). My gut instinct is that I agree with others who have already suggested that this is terminal emulation related.

Thank you to John and others for such thorough research here. I'll likely copy an El Cap version of Terminal from a backup if this doesn't get fixed soon.

Just to chime in that I am having the exact problem, rather more nastily. My terminal sometimes becomes absolutely unusable, crashes as many as every 3/4 lines of typing. It only crashes when I am typing, not when its idle. No vim, emacs or anything...just bash commands. Apple needs to fix this immediately. I feel like my problem is worsening with time.

This pretty much reproduces the crash for me. The only difference is that if I press the x's too slowly then there is no crash. For me I have to press and hold the "x" key so that the deletions are rapid fire. That guarantees a crash.

All of the reports seem center around strings that are too long/too fast coming in to terminal, regardless of source. An "x" in bash causes terminal to receive 3 characters from bash (backspace-space-backspace) to visually erase the character. The back feed is even higher if you have done "set -o vi" in bash. If you get a high repeat rate going for "x", then you got 3x that amount of chars coming back fast, which does seem to be lethal. Early in this thread there were test cases submitted to Apple. If you have Applecare, you should be able to tack yourself onto that original ticket, even if just by making a new one and cross referencing the original. If you're not covered by Applecare then you can't register interest in the ticket as far as I know.

I've switched to iterm2 from iterm2.com. It took some time to get the iterm2 settings they way I was used to them being with Apple's terminal app, but iterm2 works flawlessly for me. You might give iterm2 a try as a workaround.