Bug : Crash on Waking Computer - getting to be a regular occurrence.

Mike Binks

Any idea what happened?

Apple Crash Logs

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process: Proclaim [1407]
Path: /Applications/Proclaim.app/Contents/MacOS/Proclaim
Identifier: com.logos.Proclaim
Version: 3.5.0.0027 (315.0.27)
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2023-02-01 18:53:19.1652 +0000
OS Version: macOS 13.2 (22D49)
Report Version: 12
Anonymous UUID: 399BBFFD-15A1-7E31-E9A9-8F84DBCC61FA

Sleep/Wake UUID: 54742414-0024-4301-A68B-E0958426F273

Time Awake Since Boot: 410000 seconds
Time Since Wake: 13 seconds

System Integrity Protection: enabled

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

Exception Type: EXC_BREAKPOINT (SIGABRT)
Exception Codes: 0x0000000000000001, 0x0000000190ef87c8

....

Thread 0 Crashed:: CrBrowserMain Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x18d87a868 __pthread_kill + 8
1 libsystem_pthread.dylib 0x18d8b1cec pthread_kill + 288
2 libsystem_c.dylib 0x18d7ea2c8 abort + 180
3 libcoreclr.dylib 0x10b625540 mono_post_native_crash_handler + 20
4 libcoreclr.dylib 0x10b5e21b0 mono_handle_native_crash + 440
5 libcoreclr.dylib 0x10b6249d8 sigabrt_signal_handler + 188
6 libsystem_platform.dylib 0x18d8e02a4 _sigtramp + 56
7 libsystem_pthread.dylib 0x18d8b1cec pthread_kill + 288
8 libsystem_c.dylib 0x18d7ea2c8 abort + 180
9 libsystem_c.dylib 0x18d7e9620 __assert_rtn + 272
10 ApplicationBundle 0x106abd7ac -[ProclaimAppController exceptionHandler:shouldHandleException:mask:] + 136
11 ExceptionHandling 0x1ace9eb0c -[NSExceptionHandler _handleException] + 408
12 ExceptionHandling 0x1ace9e84c NSExceptionHandlerUncaughtSignalHandler + 44
13 libsystem_platform.dylib 0x18d8e02a4 _sigtramp + 56
14 ??? 0xffff800190ef87c0 ???
15 AppKit 0x190ef85a4 -[NSApplication reportException:] + 440
16 AppKit 0x190f928dc NSApplicationUncaughtExceptionHandler + 152
17 ExceptionHandling 0x1ace9e754 NSExceptionHandlerUncaughtExceptionHandler + 48
18 CoreFoundation 0x18daa5a08 __handleUncaughtException + 692
19 libobjc.A.dylib 0x18d55f758 _objc_terminate() + 132
20 libc++abi.dylib 0x18d869eb4 std::__terminate(void (*)()) + 20
21 libc++abi.dylib 0x18d869e50 std::terminate() + 56
22 libdispatch.dylib 0x18d72a518 _dispatch_client_callout + 40
23 libdispatch.dylib 0x18d738d1c _dispatch_main_queue_drain + 928
24 libdispatch.dylib 0x18d73896c _dispatch_main_queue_callback_4CF + 44
25 CoreFoundation 0x18d9d2d40 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 16
26 CoreFoundation 0x18d9907c0 __CFRunLoopRun + 2036
27 CoreFoundation 0x18d98f878 CFRunLoopRunSpecific + 612
28 HIToolbox 0x19706ffa0 RunCurrentEventLoopInMode + 292
29 HIToolbox 0x19706fde4 ReceiveNextEventCommon + 672
30 HIToolbox 0x19706fb2c _BlockUntilNextEventMatchingListInModeWithFilter + 72
31 AppKit 0x190c15838 _DPSNextEvent + 632
32 AppKit 0x190c149c8 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 728
33 AppKit 0x190c08df8 -[NSApplication run] + 464
34 Proclaim 0x104237b78 DesktopApplicationMain + 1260
35 Proclaim 0x104237c40 main + 12
36 dyld 0x18d587e50 start + 2544

MJ. Smith

My weekly bump of posts without responses in hopes of getting them an appropriate response.

Mike Binks

Is this connected to today's report?