You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Trying to translate Crash log

I have a user whose MacBook (running Big Sur) is crashing on our corporate webpages (among others)


From examining the Crash Logs, it looks like it is a call to:


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


But here is the whole Crash Log. I'm guessing, from what the user has reported and what I can try to make out in the log, that there might be an overall issue with either RAM or the OS install. But would appreciate a more informed insight into the log. Here is the opening, but I have included the full log as well.


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

0 libobjc.A.dylib 0x00007fff201ce9af objc_release + 15

1 com.apple.CoreFoundation 0x00007fff203e3a76 -[__NSDictionaryI dealloc] + 146

2 libobjc.A.dylib 0x00007fff201ec39d AutoreleasePoolPage::releaseUntil(objc_object**) + 167

3 libobjc.A.dylib 0x00007fff201cf33e objc_autoreleasePoolPop + 161

4 com.apple.CoreFoundation 0x00007fff203e91f0 _CFAutoreleasePoolPop + 22

5 com.apple.CoreFoundation 0x00007fff204f2748 __CFRunLoopPerCalloutARPEnd + 41

6 com.apple.CoreFoundation 0x00007fff2042788b __CFRunLoopRun + 2788

7 com.apple.CoreFoundation 0x00007fff204266ce CFRunLoopRunSpecific + 563

8 com.apple.Foundation 0x00007fff211b3fa1 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 212

9 com.apple.Foundation 0x00007fff21242384 -[NSRunLoop(NSRunLoop) run] + 76

10 com.apple.authorizationhost 0x0000000104016727 main + 302

11 libdyld.dylib 0x00007fff2034b621 start + 1



Posted on Jan 15, 2021 3:20 PM

Reply
Question marked as Top-ranking reply

Posted on Jan 28, 2021 1:43 AM

Then, unfortunately, its looking more likely this was a User-instigated botched upgrade. Happens a lot. Given the current situation its difficult to see how it can be resolved quickly and easily unless user gives you their computer and you do the upgrade, properly.


Remember this is an upgrade and not an update. Two different things entirely.


Alternatively user follows Apple's upgrade guidelines here: How to upgrade to macOS Big Sur – Apple Support and has another go themselves.


Preferably using a wired connection rather than Wi-Fi. Better still I would advise a fully bootable back-up (clone using CarbonCopyCloner) first, followed by a wipe/format and clean install of macOS. That way you're starting from a clean slate with no crud & cruft that builds up over time lurking in the background waiting to fubar the computer. If it goes badly (as it has done in this case) the user can revert back to a known good working state using the clone. If user did not do a back-up prior to upgrading (as he/she should have done) then its going to take longer. If doing a format/clean install then from there re-install/re-download (not copied over) clean copies of software user needs and re-instate from scratch email and any other accounts etc the user needs for their work.


Again these are all things best handled (in general) by the IT department. Did you confirm if this was a company owned computer or one owned by the user?


Good luck

Similar questions

5 replies
Question marked as Top-ranking reply

Jan 28, 2021 1:43 AM in response to garnth

Then, unfortunately, its looking more likely this was a User-instigated botched upgrade. Happens a lot. Given the current situation its difficult to see how it can be resolved quickly and easily unless user gives you their computer and you do the upgrade, properly.


Remember this is an upgrade and not an update. Two different things entirely.


Alternatively user follows Apple's upgrade guidelines here: How to upgrade to macOS Big Sur – Apple Support and has another go themselves.


Preferably using a wired connection rather than Wi-Fi. Better still I would advise a fully bootable back-up (clone using CarbonCopyCloner) first, followed by a wipe/format and clean install of macOS. That way you're starting from a clean slate with no crud & cruft that builds up over time lurking in the background waiting to fubar the computer. If it goes badly (as it has done in this case) the user can revert back to a known good working state using the clone. If user did not do a back-up prior to upgrading (as he/she should have done) then its going to take longer. If doing a format/clean install then from there re-install/re-download (not copied over) clean copies of software user needs and re-instate from scratch email and any other accounts etc the user needs for their work.


Again these are all things best handled (in general) by the IT department. Did you confirm if this was a company owned computer or one owned by the user?


Good luck

Jan 15, 2021 4:27 PM in response to garnth

It’s hard to see it being RAM related if it’s only crashing when accessing websites, corporate or otherwise? Presumably the user is using Safari when this happens? Have you suggested he/she try using other browsers? Or at least the same browser that everyone else is using.


I could be wrong but this may be related to your network’s security requirements? The crash log shows repeated calls to the Kerberos framework. Presumably this is an SSO (Single Sign On) environment, probably Active Directory, with a somewhat restrictive proxy in place? Does the problem disappear when on the wireless network or does it only happen on the wired one? Is this the only Mac on the network or is it the only one affected? If the only one how are the others different? EG: same spec, different OS etc. Have you installed all the corporate network‘s certificates? Is the user authenticating with their assigned network user ID properly or is he/she confused about which ID they should be using? Is this a new Mac with Big Sur pre-installed or a recent upgrade from a previous OS? Is this the User’s own machine or one belonging to the enterprise? Apologies for all the questions but some answers are needed before we can help you narrow it down to something more specific.

Jan 22, 2021 5:00 PM in response to Antonio Rocco

Thank you for the response.



The machine was upgraded to Big Sur from Catalina by the user, at which time the crashes/performance issues began. I can't speak to the wireless/wired as the user is (unsurprisingly) working from home and doesn't have a hard wired connection available to them.


All other domain/corporate functionality is good - including other internal security processes, like VPN and Exchange connectivity that relies upon properly installed certificates.


We have worked with the user to confirm that there isn't a BUAK error occurring in the username/password information - even having the user enter the credentials on a remote session on another machine (Windows, not Mac) and access is fine. The crashes only began after the Big Sur update - and since the machine doesn't host the M1 chip (as it is a previous generation MacBook) perhaps that is the issue.

Trying to translate Crash log

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.