Notification Center crashes in Big Sur

Question

Created Nov ’20

Replies 9

Boosts 0

Views 3.1k

Participants 9

Hi,

The last week I've upgraded my Mac Mini (2018) to Big Sur and the Notification Center started crashing once per second:

Code Block Nov 26 10:17:17 ---- NotificationCenter[36862]: objc[36862]: Class NCCAFenceWrapper is implemented in both /System/Library/PrivateFrameworks/NotificationCenterUI.framework/Versions/A/NotificationCenterUI and /System/Library/CoreServices/NotificationCenter.app/Contents/MacOS/NotificationCenter. One of the two will be used. Which one is undefined.
Nov 26 10:17:17 ---- NotificationCenter[36862]: objc[36862]: Class NCJSONTransformer is implemented in both /System/Library/Frameworks/NotificationCenter.framework/Versions/A/NotificationCenter and /System/Library/CoreServices/NotificationCenter.app/Contents/MacOS/NotificationCenter. One of the two will be used. Which one is undefined.
Nov 26 10:17:17 ---- com.apple.xpc.launchd[1] (com.apple.notificationcenterui.agent[36862]): Service exited due to SIGILL | sent by exc handler[36862]
Nov 26 10:17:17 ---- com.apple.xpc.launchd[1] (com.apple.notificationcenterui.agent): Service only ran for 0 seconds. Pushing respawn out by 1 seconds.

I've lots of crashes in the console and I cannot run the Notification Center from the Terminal:

Code Block /System/Library/CoreServices/NotificationCenter.app/Contents/MacOS/NotificationCenter      
objc[34799]: Class NCCAFenceWrapper is implemented in both /System/Library/PrivateFrameworks/NotificationCenterUI.framework/Versions/A/NotificationCenterUI and /System/Library/CoreServices/NotificationCenter.app/Contents/MacOS/NotificationCenter. One of the two will be used. Which one is undefined.
objc[34799]: Class NCJSONTransformer is implemented in both /System/Library/Frameworks/NotificationCenter.framework/Versions/A/NotificationCenter and /System/Library/CoreServices/NotificationCenter.app/Contents/MacOS/NotificationCenter. One of the two will be used. Which one is undefined.
[1]  34799 illegal hardware instruction

I've used the Feedback Application to report this but no one seams to look at it.

The crashes looks like this:

Code Block Process:               NotificationCenter [32062]
Path:                  /System/Library/CoreServices/NotificationCenter.app/Contents/MacOS/NotificationCenter
Identifier:            NotificationCenter
Version:               1.0 (1108.10.3)
Build Info:            NotificationCenter-1108010003000000~4
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           NotificationCenter [32062]
User ID:               501
Date/Time:             2020-11-26 10:05:23.758 +0100
OS Version:            macOS 11.0.1 (20B29)
Report Version:        12
Bridge OS Version:     5.0.1 (18P2561)
Anonymous UUID:        3582C5C4-6B74-D757-B804-BEA6E55F8AD9
Sleep/Wake UUID:       84D2CF11-604E-4606-849D-B1756B33D6E2
Time Awake Since Boot: 5900 seconds
Time Since Wake:       160 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 [32062]
Application Specific Information:
dyld3: launch started
container_create_or_lookup_for_current_user(): 109
Application Specific Signatures:
container_create_or_lookup_for_current_user(): 109
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_secinit.dylib       	0x00007fff2a4dd0a3 _libsecinit_appsandbox.cold.5 + 49
1   libsystem_secinit.dylib       	0x00007fff2a4dc492 _libsecinit_appsandbox + 1924
2   libsystem_trace.dylib         	0x00007fff20086ee8 _os_activity_initiate_impl + 51
3   libsystem_secinit.dylib       	0x00007fff2a4dbccd _libsecinit_initializer + 67
4   libSystem.B.dylib             	0x00007fff2a4f168b libSystem_initializer + 272
5   libdyld.dylib                 	0x00007fff2031925c invocation function for block in dyld3::AllImages::runAllInitializersInImage(dyld3::closure::Image const*, dyld3::MachOLoaded const*) + 159
6   libdyld.dylib                 	0x00007fff20319142 dyld3::closure::Image::forEachInitializer(void const*, void (void const*) block_pointer) const + 84
7   libdyld.dylib                 	0x00007fff203316cb dyld3::AllImages::runLibSystemInitializer(dyld3::LoadedImage&) + 107
8   libdyld.dylib                 	0x00007fff20343b09 dyld3::entry_setInitialImageList(dyld3::closure::LaunchClosure const*, DyldSharedCache const*, char const*, dyld3::Array<dyld3::LoadedImage> const&, dyld3::LoadedImage&) + 65
9   dyld                          	0x0000000113559f22 dyld::launchWithClosure(dyld3::closure::LaunchClosure const*, DyldSharedCache const*, dyld3::MachOLoaded const*, unsigned long, int, char const, char const, char const**, Diagnostics&, unsigned long*, unsigned long*, bool*, bool*) + 1682
10  dyld                          	0x0000000113556c89 dyld::_main(macho_header const*, unsigned long, int, char const, char const, char const**, unsigned long*) + 4933
11  dyld                          	0x000000011355022b dyldbootstrap::start(dyld3::MachOLoaded const*, int, char const**, dyld3::MachOLoaded const*, unsigned long*) + 457
12  dyld                          	0x0000000113550025 _dyld_start + 37

Anyone is having problems with the Notification Center in Big Sur too?

Many thanks

Boost

Answer 1

david_treblig OP

Dec ’20

Yup I posted about the same bug. Someone mentions that it might be only with an external monitor plugged in (possibly when discrete gpu is enabled, but that's just an instinct of mine having had many issues over the years with those).

0

Answer 2

eboschhabit OP

Dec ’20

Well, it didn't happen before Big Sur and I'm with a Mac Mini, so I need an external display 😅

¿Anyone know how to solve this?

0

Answer 3

ivantodorov OP

Dec ’20

This happens to me on a 16" MBP with XDR Display every time I click on the date to "open" the notification slide out, and try to "clear all" notifications. Super annoying having to use the Activity Monitor to Force-Quit it.

0

Answer 4

dsubar OP

Dec ’20

Having the same problem. I think it is only when I have an external monitor attached but I am not certain.

0

Answer 5

shahasad78 OP

Jan ’21

The same is happening on my MacBook Pro 16" running Big Sur with no external display plugged in. Right now it shows that I am using the Intel UHD graphics.

0

Answer 6

esaad91 OP

Jan ’21

I have the same issue. In fact, my notification centre doesn't work at all. If I open it, it just hangs and the spinning rainbow wheel shows. Rather than killing it from activity monitor I just run killall NotificationCenter from terminal.

0

Answer 7

ck3mp OP

Feb ’21

This came up today for me too... MacBook Pro 2020 Apple Silicon... just froze and shows the spinning wheel when I move the mouse to the edge of the screen. Also using external display via Thunderbolt

0

Answer 8

travishalff OP

Apr ’21

Has anyone found a fix to this? The terminal command works to unfreeze, but after clearing another set of notifications or two it freezes up again. Sometimes I won't even be able to trigger the flyout because it has frozen.

0

Answer 9

dustbuster42 OP

May ’21

I had the same issue, my Mac's Notification Center App was crashing as soon as I would start my computer. To fix it, I quit the NC App in Activity Monitor, waited for it to reboot and cleared all of my email notifications, the NC stopped crashing. I supposed because I had so many emails in there that I did not clear it would just over-run the application with data. I have never had to do that before Big Sur. Hope this helps someone.

0