Terminal.app crashing: Can I disable callbacks?

Hi John,

Still no crashes for me using secure text entry, but I have been using vi only lightly for the past week and due to the holidays have not even been in front of my office desktop that much. Given what Sakuro has reported, however, I consider this cake pretty well baked (or rather, burnt). I will be back in the office and using vi more heavily next week and will continue testing secure text entry for the **** of it, but I think Sakuro has already put this grasped straw to bed. I believe Sakuro's test involves tail'ing an active log file from a running nginx web server into Terminal, so I can't see any way to duplicate that activity myself or I would gladly try -- Sakuro, if I have misunderstood and there is some static file you can send me which will reproduce the problem on my system I am certainly willing to attempt that.

Not surprising to me that an ElCap Terminal.app may fix the problem given that all evidence so far points to the bug clearly being resident within the Sierra Terminal.app. I suppose it is still possible, however, that the bug is in some shared lib accessed by Sierra's Terminal which is NOT accessed by ElCap's.

I would again exhort everyone who is following this thread to send every single crash dump they get to Apple -- the sooner their in-box fills up the quicker we will get some attention.

Thanks to all (and to John in particular) for their continuing efforts to follow up on this annoyance!

Roger

More idle speculation on my part ...

I think Sakuro's crashes may be the first example we have seen where there has been no actual input keystroke processing by Terminal anywhere close to the time of the crash (i.e., it appears that nothing has been typed for several seconds to several minutes after the command 'tail -f ....' is entered). The crash seems to be triggered purely by output from a running child process which is causing Terminal to redraw. So, as Sakuro has suggested, the problem may indeed be triggered by the curses library embedded within vi/tmux/whatever. Let's keep in mind, however, that it's Terminal that is crashing so it seems that the actual bug may be Terminal's inability to graciously handle or refuse whatever (possibly strange) redraw request is being made by its children.

Hi folks, just chiming in to say that I upgraded to 10.12.2 the other day & am now being hit by this problem repeatedly. As it happens, I'm ssh'ed in to a remote box & running vim on that box. Seems to happen to me most frequently when I'm doing a lot of arrowing around (i.e. sending a lot of keystrokes fairly quickly).

I don't have a machine with El Cap & thus don't have a copy of an older Terminal.app handy. It makes no difference on my machine whether I have "Secure Keyboard Entry" enabled or disabled.

I have the same problem after upgrading to Sierra 10.2.2: Terminal.app crashes every few minutes while running /usr/bin/vim. This may be anecdotal: seems to happen right after a copy-paste from another Terminal window, where the copied text is usually plain-jane (7-bit) ascii and less than 80 characters long (although there are other crash-capable cases with unicode characters and/or strings up to 150 characters). I am unable to find the El Capitan version of Terminal.app so I am going to try using the XQuartz 'term' program (clunky, but it does the job and doesn't crash).

I am seeing crashes every time I ssh to a remote host and then run "screen -r". I would be happy to provide any diagnostics that could help solve the issue.

It seems running peacefully after one hour long tailing.

'tail -f' is running happily for 4 hours in El Capitan's Terminal.app($TERM_PROGRAM_VERSION is 377) on Sierra without crash.

It will be a workaround until the issue is fixed.

Beautiful, ProValid, thanks a million!! Confirmed on my system as well.

Apple? Hello?? Can you please fix this now???

I was also using Cisco AnyConnect VPN and ssh'ing into a screen session when seeing this behavior.

10.12.3 beta 4 just released and I tested it - no fix yet.

I just installed 10.12.3 on my test machine - it's not fixed 😟

The Applescript still crashes Terminal.

Hi,

I'm having the same problems with Terminal and vim.

Thanks for all the investigations.

Looks like we need to wait for a fix, as per RogerDavis' post of Jan 6th. I'll be watching this thread.

@hkoster1: that is strange, because vim help says that the wm option is not used if textwidth is set. So if you're using textwidth, removing wm should have no effect, right?

Just installed the 10.12.4 beta 1 - no dice - still crashes.

me too. running screen on a bunch of terminal windows, using vi within screen. happens a lot when changing focus with mouse from one terminal window to another.