CrashReporter closes before I can Send to Apple (and see the report)

Question

Level 1

10 points

CrashReporter closes before I can Send to Apple (and see the report)

BACKGROUND:

I have a MacBook Pro 13, 2 (Retina, TouchBar) that crashes more often than I'd hope, often related to sleep/wake failures. I've reinstalled macOS (10.13.6 currently) twice over time. I get the feeling that sometimes after I shut the lid, it crashes. Happened overnight. Lifted the lid this morning, and was at a login screen; it had rebooted.

PROBLEM:

CrashReporter opened, and I tried to click Send to Apple (mainly so I could capture the report), however apps were still opening, and I couldn't click the button fast enough, and after all apps had opened, the CrashReporter window was gone.

QUESTIONS:

1) Is it possible to open CrashReporter from the Finder? I've read on this forum it is a daemon, so that may not be possible.

2) If I *could* open it, is there any way to display what it was trying to show my when it was open, or is that information sort of past-history, as far as CrashReporter is concerned?

MORE INFO:

I've looked in Console as well as logs (in Finder), and have found some relevant information related to the crash, however the report that CrashReporter displays seems to display the relevant information much better than the logs I've looked at, and omits irrelevant information.

MacBook Pro 13", macOS 10.13

Posted on Feb 29, 2020 9:22 AM

Reply

Answer 1

Top-ranking reply

EcoGreg

Level 3

894 points

Mar 1, 2020 9:50 AM in response to bob7

Hi Bob

Try changing the Apple reporting in System Preferences>Privacy>Analytics and deselect Share Mac Analytics. If this is selected it will automatically send and the report pop-up will only briefly show then disappear. If you uncheck, Send to Apple, then when a crash happens, a report window will appear that will not be dismissed until you click Send to Apple.

You should be able to view the crash reporter and other logs. These reports are reverse chronological order so your issues should be near the top and will show error/failure.

An app that may help is EtreCheck.

Apple changed how Console works, so is much more confusing. One hint is to note the time the an issue occurs, then in Console you can search for issues around the time of problem. Otherwise console is way too busy IMHO, it is showing all activities not just "Crashes"..

Hope this Helps, Greg

Reply

Answer 2

BDAqua

Level 10

250,773 points

Feb 29, 2020 10:09 AM in response to bob7

Hello Bob,

It won't do any good to send them to Apple, 10.13.6 is close to dead as far as they're concerned.

https://macreports.com/crash-reports-how-to-use-them-to-troubleshoot-why-your-mac-crashed/

Or...

EtreCheck is a simple little app to display the important details of your system configuration and allow you to copy that information to the Clipboard. It is meant to be used with Apple Support Communities to help people help you with your Mac.

http://www.etresoft.com/etrecheck

Pastebin is a good place to paste the whole report...

https://pastebin.com/

Or use the paperclip at the bottom of a Reply to attach the full report here. :)

Workable but harder for me to work with...the Note tool on the bottom of this editor's toolbar, as shown in the image, to copy and paste the output from EtreCheck.

There is also free Malwarebytes which may take care of it...

https://www.malwarebytes.com/mac/

Reply

Answer 3

bob7 Author

Level 1

10 points

Feb 29, 2020 10:22 AM in response to BDAqua

Very helpful, thank you. What you wrote about Apple seems to be in line with what their support told me: upgrade to 10.15: 'it will solve many problems'. (Note: I have an active AppleCare contract) The problems I have with this are:

1) If my MacBook Pro has hardware problems (like sleep/wake -lid) unrelated to the OS (the TouchBar also fails to work at times (adjusting volume)), I shouldn't have to upgrade from 10.13.6, which should still be supported by Apple on this device. It's not as if I bought a new Mac and then downgraded the OS. (I could look into compatibility with 10.14, however.)

2) I have apps that are critical to me and that won't run under 10.14 (and I am not going to set up a VM with 10.13 under 10.15).

My venting is not directed at you, of course. I'll look into your suggestions.

Reply

Answer 4

BDAqua

Level 10

250,773 points

Mar 1, 2020 5:51 PM in response to bob7

Good work Bob...

Does yours qualify for Keyboard Service Program for MacBook, MacBook Air, and MacBook Pro...

https://support.apple.com/keyboard-service-program-for-mac-notebooks

Eligible Models

To identify your computer's model and to see if it is eligible for this program, choose Apple () menu > About This Mac. Eligible models are listed below.

▪ MacBook (Retina, 12-inch, Early 2015)

▪ MacBook (Retina, 12-inch, Early 2016)

▪ MacBook (Retina, 12-inch, 2017)

▪ MacBook Air (Retina, 13-inch, 2018)

▪ MacBook Pro (13-inch, 2016, Two Thunderbolt 3 Ports)

▪ MacBook Pro (13-inch, 2017, Two Thunderbolt 3 Ports)

▪ MacBook Pro (13-inch, 2016, Four Thunderbolt 3 Ports)

▪ MacBook Pro (13-inch, 2017, Four Thunderbolt 3 Ports)

▪ MacBook Pro (15-inch, 2016)

▪ MacBook Pro (15-inch, 2017)

▪ MacBook Pro (13-inch, 2018, Four Thunderbolt 3 Ports)

▪ MacBook Pro (15-inch, 2018)

▪ MacBook Pro (13-inch, 2019, Four Thunderbolt 3 Ports)

▪ MacBook Pro (15-inch, 2019)

Note: No other Mac notebook models are part of this program.

https://www.apple.com/support/keyboard-service-program-for-mac-notebooks/

Reply

Answer 5

BDAqua

Level 10

250,773 points

Feb 29, 2020 11:59 AM in response to bob7

Yeah, understood... etrecheck report may or may not help us. :)

Reply

Answer 6

BDAqua

Level 10

250,773 points

Mar 1, 2020 3:18 PM in response to EcoGreg

Thanks Greg! :)

Reply

Answer 7

bob7 Author

Level 1

10 points

Mar 1, 2020 5:57 PM in response to BDAqua

It appears mine is one of those. I'll check it out. Thanks.

Reply

Answer 8

bob7 Author

Level 1

10 points

Mar 1, 2020 5:39 PM in response to BDAqua

I tried to make that change in Mac Analytics. When I attempted to authorize changes, the padlock was grey for at least minutes, and System Preferences seemed to be unresponsive. I was somehow able to get it to quit (once using Activity Monitor); it never showed as unresponsive using cmd-opt-esc. Anyway, I later shut the lid and unplugged from power (with 100% charge). When I opened the lid, it restarted. Interestingly, the 'send to Apple' restart/crash dialog never showed up. When I went to SysPref to deselect Share Mac Analytics, it was unchecked. Maybe the change I tried to affect actually stuck.

In Console > User Reports I found a crash report corresponding to the crash. Following is the first part of the report.

Assuming ControllStrip is the TouchBar, I've had many problems with the TouchBar not working as expected.

I'm still hoping to get Crash Reporter to work.

ControlStrip_2020-03-01-073717_Administrators-MacBook-Pro.crash

Application Specific Information:

Process: ControlStrip [925]

Path: /System/Library/CoreServices/ControlStrip.app/Contents/MacOS/ControlStrip

Identifier: com.apple.controlstrip

Version: 1.0 (175.2)

Build Info: ControlStrip-175002000000000~3

Code Type: X86-64 (Native)

Parent Process: ??? [1]

Responsible: ControlStrip [925]

User ID: 503

Date/Time: 2020-03-01 07:37:12.136 -0800

OS Version: Mac OS X 10.13.6 (17G11023)

Report Version: 12

Bridge OS Version: 3.0 (14Y901)

Anonymous UUID: 92E63ECF-6E96-7158-EBF5-32DCBBB3700C

Sleep/Wake UUID: 2A4F9F3C-B0C7-47B6-B3CD-322953016368

Time Awake Since Boot: 62000 seconds

Time Since Wake: 32000 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_INSTRUCTION (SIGILL)

Exception Codes: 0x0000000000000001, 0x0000000000000000

Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Illegal instruction: 4

Termination Reason: Namespace SIGNAL, Code 0x4

Terminating Process: exc handler [0]

Application Specific Information:

Crashing on exception: 604769831.714096 Missing Touches. This is a bug in IOHIDFamily

Reply

Answer 9

BDAqua

Level 10

250,773 points

Mar 1, 2020 6:19 PM in response to bob7

Yeah, I think the V was not a good idea as it turned out.

Reply

CrashReporter closes before I can Send to Apple (and see the report)

Similar questions