Terminal.app crashing: Can I disable callbacks?

New topics:

• Sierra 10.12.2: Has it been offered to you Roger? Software update keeps offering me only 10.12.1. Perhaps they are prioritizing distribution of the update to those who have the newest model laptop.
• Vim Forum: I posted a summary to https://groups.google.com/forum/#!forum/vim_mac but the post has not yet been approved for publication.

Updates to previous topics:

• Crash stack: Roger, I think that your stack looks similar (identical in all but the final leaf?) to what I called 'signature 2' in the summaries that I posted (upthread from Dec 8, 2016 3:21 PM)
• System Integrity Protection: I have NOT changed system integrity protection from its default; though I considered it because dtrace (upthread Dec 9, 2016 6:19 AM)
• Workaround candidates: as you point out, we lack a clear reproducer, and just need to put time into workarounds and hope that one removes the random-seeming crashes.
  • Secure text entry: thank you for testing this potential workaround; let us know how it goes. (Drew suggested this Dec 16, 2016 10:05 AM)
  • Vim 7.3: I will continue testing that one. (Recipe at entry from Dec 16, 2016 10:40 AM)

Sierra 10.12.latest

Roger: Darwin Kernel Version 16.3.0: Thu Nov 17 20:23:58 PST 2016; root:xnu-3789.31.2~1

Mine: Darwin Kernel Version 16.1.0: Wed Oct 19 20:31:56 PDT 2016; root:xnu-3789.21.4~4

Yours is newer.
Well, there goes my hope that there will be a bugfix whenever it gets around to offering me 10.12.2.

Sidebar: is mine 'stuck' at 10.12.1?

It has offered me lots of updates, and I have installed all of them. I don't know why it won't offer 10.12.2

The screen at App Store won't let me cut/paste, so forgive typos. It says:

I don't know how it managed to install iMovie while it was on the truck :-)

But that is what it says.

Here are the records from 'last'.

I took it out of the UPS packaging and the shrinkwrap on Friday the 2nd.

November 24th, I suppose, was at manufacturing.

$ last | tail -14 jhenning console Fri Dec 2 14:46 - crash (21:41) _mbsetupuser console Fri Dec 2 14:43 - crash (21:44) root console Fri Dec 2 14:43 - 14:43 (00:00) reboot ~ Fri Dec 2 14:43 _mbsetupuser console Fri Dec 2 10:01 - crash (04:41) admin console Fri Dec 2 09:42 - crash (05:00) _mbsetupuser console Fri Dec 2 09:41 - crash (05:02) root console Fri Dec 2 09:41 - 09:41 (00:00) reboot ~ Fri Dec 2 09:40 _mbsetupuser console Thu Nov 24 18:29 - crash (7+15:11) root console Thu Nov 24 18:29 - 18:29 (00:00) reboot ~ Thu Nov 24 18:28 wtmp begins Thu Nov 24 18:28 $

Fascinating. The 24th was the day that I ordered it. Thus on the 24th, the laptop was apparently not sitting on a B&H shelf already shrink-wrapped; it was somewhere in a pipeline ready to have an OS installed, ready to be shrinken.

Maybe B&H doesn't actually stock anything but just places its own system-specific orders with Apple when they (B&H) get your order?

Yes. Or some intermediate entity who owns a shrink wrapper and is entitled to sell as 'new'.

The reason this seems fascinating to me is that the touch bar model was announced 4 weeks prior (27-Oct); I had difficulty finding anyone who had the old model available; but B&H claimed 'in stock' and status 'new'.

Thus, I was expecting that I would get a laptop that had been shrink-wrapped at least one month prior.

Well Hello(!) Mr. Chan-nui, and since you mention tmux, that tells me which Chan-nui I am speaking to :-)

Workaround candidates at this point

• Vim 7.3: Just now, I have seen a Terminal crash whilst using Vim 7.3; so that rules out that workaround.
• Secure Text Entry: Roger is trying this suggestion, from Drew, who suggested it Dec 16, 2016 10:05 AM. Let us know how it goes.
• Old Terminal: I have hesitated to try this for fear of incurring the wrath of some system protection that I do not understand; but am at last trying it. Considering that (for all I know) such (hypothetical) wrath might depend upon details of how it is installed and invoked, I record the detail of the attempt here:
  • Finder / Go / Applications

    File / New Folder 'FromOldDisk'

  • Finder / File / New Finder Window
    • click over to usb copy of El Capitan disk / Applications / Utilities
    • control-click Terminal.app / copy Terminal.app
  • Back to first finder window
    • double-click folder FromOldDisk
    • control-click / Paste Item
    • double-click Terminal.app (within the FromOldDisk folder)
  • Something came up. What is it?

$ me=$$ $ parent=$(ps -o ppid= -p $me) $ grandparent=$(ps -o ppid= -p $parent) $ ps -o pid,ppid,stime,comm -p $me,$parent,$grandparent PID PPID STIME COMM 1219 1 0:00.99 /Applications/FromOldDisk/Terminal.app/Contents/MacOS/Terminal 1222 1219 0:00.01 login 1223 1222 0:00.04 -bash

Thus demonstrating that indeed the OLD one is running; also confirmed by Terminal / About Terminal: 2.6.1 (361.1), vs. the Sierra 2.7.1 (387))

I will report as to whether this is, at last, a viable workaround.

No crashes during first 10+ hours of using workaround 'Old Terminal'.

Tentatively, I am hopeful.

Hi Broomdodger, Yes, I have used MacVim, but not recently; the adventures documented here are strictly /usr/bin/vi

Summary of thread thus far

• Apple case # 100085116387 was filed on 8-Dec
  • The senior support representative was kind, but warned that there might not be quick action
  • If anyone else files a ticket, please ask the representative to cross reference it with the above.
• Five users report the crashes of Terminal.app (thus far)
• My crashes happened withSierra 10.12.1, but others have reported 10.12.2
• I have seen the crashes in:
  • Migrated account, and
  • Fresh new account, and
  • Safe mode, and
  • Wiped disk on other laptop.
• Other failed workarounds:
  • Use vim 7.3 from El Capitan (still saw crashes)
  • Update Cisco VPN (still saw crashes + subsequently excluded as a candidate by the wiped-disk-other-laptop test))

• No reproducer exists at this time, and it is hard to get data on the circumstances
  • It would be nice if there were truss or dtrace logs
  • A link above (Dec 9, 6:19am) allegedly explains how to enable dtrace, but I have not dared.
  • The stack traces are not obviously insane when compared to 'normal' running app. (see entry Dec 8 at 7:19pm)
  • Maybe 'fs_usage' could provide clues?
• The evidence suggests that although Vim is commonly the victim, it is not likely to be the criminal, because
  • Crashes happened with older Vim (7.3)
  • Both Mr. Chan-nui and Sakuro-san report crashes with tmux

Workaround candidates remaining

• Old Terminal: (described Dec 18 at 6:22pm) No crashes yet. Anyone else want to try it too? If so, please report whether it helps.
• Secure Text Entry: Roger is trying this suggestion, from Drew, who suggested it Dec 16, 2016 10:05 AM. Let us know how it goes.