On-Core Software LLC
SnoozeMaster => General Discussion => Topic started by: netlogic on October 20, 2019, 08:49:22 am
-
Hi and good morning,
I have also emailed this content to support@on-core.com (forgive the double post)
I have been using Snoozemaster for years and it is invaluable.
This week it stared crashing on startup.
I have attached the crash report.
Any ideas on how to get around crash?
Will this app be updated soon and if not can it be made open source so I can fix the crash (I am a developer)?
Thank you for your help,
Bret
Process: SnoozeMaster [9439]
Path: /Applications/SnoozeMaster.app/Contents/MacOS/SnoozeMaster
Identifier: com.oncore.snoozemaster
Version: 1.9.2 (2.0.1)
App Item ID: 614955483
App External ID: 816383238
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: SnoozeMaster [9439]
User ID: 501
Date/Time: 2019-10-18 07:28:16.325 -0400
OS Version: Mac OS X 10.14.6 (18G95)
Report Version: 12
Bridge OS Version: 3.6 (16P6571)
Anonymous UUID: A43A2614-22A9-367B-202C-B85ECC7DD994
Sleep/Wake UUID: 539BB359-5D67-4F2E-B9BE-3C3A2042FB8B
Time Awake Since Boot: 2200000 seconds
Time Since Wake: 660 seconds
System Integrity Protection: enabled
Crashed Thread: 5 Dispatch queue: com.apple.root.background-qos
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Application Specific Information:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSCFCalendar dateFromComponents:]: components cannot be nil'
abort() called
terminating with uncaught exception of type NSException
Application Specific Backtrace 1:
0 CoreFoundation 0x00007fff310702fd __exceptionPreprocess + 256
1 libobjc.A.dylib 0x00007fff5b744a17 objc_exception_throw + 48
2 CoreFoundation 0x00007fff3105bf8d __CFStringsDictMergeApplyFunction + 0
3 CoreFoundation 0x00007fff3105ba77 -[_NSCopyOnWriteCalendarWrapper dateFromComponents:] + 69
4 SnoozeMaster 0x000000010e2154f7 SnoozeMaster + 29943
5 SnoozeMaster 0x000000010e2117d1 SnoozeMaster + 14289
6 SnoozeMaster 0x000000010e21324c SnoozeMaster + 21068
7 libdispatch.dylib 0x00007fff5cec45f8 _dispatch_call_block_and_release + 12
8 libdispatch.dylib 0x00007fff5cec563d _dispatch_client_callout + 8
9 libdispatch.dylib 0x00007fff5ced3509 _dispatch_root_queue_drain + 657
10 libdispatch.dylib 0x00007fff5ced3b46 _dispatch_worker_thread2 + 90
11 libsystem_pthread.dylib 0x00007fff5d1056b3 _pthread_wqthread + 583
12 libsystem_pthread.dylib 0x00007fff5d1053fd start_wqthread + 13
Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff5d04722a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff5d04776c mach_msg + 60
2 com.apple.CoreFoundation 0x00007fff30fba1ee __CFRunLoopServiceMachPort + 328
3 com.apple.CoreFoundation 0x00007fff30fb975c __CFRunLoopRun + 1612
4 com.apple.CoreFoundation 0x00007fff30fb8ebe CFRunLoopRunSpecific + 455
5 com.apple.HIToolbox 0x00007fff302181ab RunCurrentEventLoopInMode + 292
6 com.apple.HIToolbox 0x00007fff30217ee5 ReceiveNextEventCommon + 603
7 com.apple.HIToolbox 0x00007fff30217c76 _BlockUntilNextEventMatchingListInModeWithFilter + 64
8 com.apple.AppKit 0x00007fff2e5b079d _DPSNextEvent + 1135
9 com.apple.AppKit 0x00007fff2e5af48b -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361
10 com.apple.AppKit 0x00007fff2e5a95a8 -[NSApplication run] + 699
11 com.apple.AppKit 0x00007fff2e598ae8 NSApplicationMain + 777
12 libdyld.dylib 0x00007fff5cf123d5 start + 1
Thread 1:
0 libsystem_pthread.dylib 0x00007fff5d1053f0 start_wqthread + 0
Thread 2:
0 libsystem_pthread.dylib 0x00007fff5d1053f0 start_wqthread + 0
Thread 3:: Dispatch queue: XPCConnectionManager:0x7fba08f4a880
0 libsystem_kernel.dylib 0x00007fff5d04722a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff5d04776c mach_msg + 60
2 libdispatch.dylib 0x00007fff5ced93e7 _dispatch_mach_send_and_wait_for_reply + 609
3 libdispatch.dylib 0x00007fff5ced9882 dispatch_mach_send_with_result_and_wait_for_reply + 50
4 libxpc.dylib 0x00007fff5d144647 xpc_connection_send_message_with_reply_sync + 178
5 com.apple.Foundation 0x00007fff3320a7b6 __NSXPCCONNECTION_IS_WAITING_FOR_A_SYNCHRONOUS_REPLY__ + 9
6 com.apple.Foundation 0x00007fff33209bd5 -[NSXPCConnection _sendInvocation:orArguments:count:methodSignature:selector:withProxy:] + 4551
7 com.apple.Foundation 0x00007fff33254508 -[NSXPCConnection _sendSelector:withProxy:arg1:arg2:] + 125
8 com.apple.Foundation 0x00007fff33254485 _NSXPCDistantObjectSimpleMessageSend2 + 46
9 com.apple.CoreData 0x00007fff30df6261 -[NSXPCStoreConnection sendMessage:store:error:] + 401
10 com.apple.CoreData 0x00007fff30df6748 -[NSXPCStoreConnection sendMessageWithContext:] + 88
11 com.apple.CoreData 0x00007fff30c978f4 __54-[NSXPCStoreConnectionManager sendMessageWithContext:]_block_invoke + 100
12 libdispatch.dylib 0x00007fff5cec563d _dispatch_client_callout + 8
13 libdispatch.dylib 0x00007fff5ced1642 _dispatch_sync_invoke_and_complete + 60
14 com.apple.CoreData 0x00007fff30c97886 -[NSXPCStoreConnectionManager sendMessageWithContext:] + 86
15 com.apple.CoreData 0x00007fff30dc5ce1 -[NSXPCStore sendMessage:fromContext:interrupts:error:] + 513
16 com.apple.CoreData 0x00007fff30dc836e -[NSXPCStore executeFetchRequest:withContext:error:] + 654
17 com.apple.CoreData 0x00007fff30dc9c9e -[NSXPCStore executeRequest:withContext:error:] + 94
18 com.apple.CoreData 0x00007fff30bf9680 __65-[NSPersistentStoreCoordinator executeRequest:withContext:error:]_block_invoke + 2304
19 com.apple.CoreData 0x00007fff30bf0960 -[NSPersistentStoreCoordinator _routeHeavyweightBlock:] + 288
20 com.apple.CoreData 0x00007fff30b25607 -[NSPersistentStoreCoordinator executeRequest:withContext:error:] + 1287
21 com.apple.CoreData 0x00007fff30b23641 -[NSManagedObjectContext executeFetchRequest:error:] + 993
22 com.apple.CalendarPersistence 0x00007fff4261aded -[CalManagedObjectContext executeFetchRequest:error:] + 71
23 com.apple.ical.EventKit 0x00007fff330f235d -[EKCalendarStoreBackingStore _fetchFrozenMasterOrDetachedEventsInRange:inCalendars:forceNonPartial:] + 330
24 com.apple.ical.EventKit 0x00007fff3304b4c8 __69-[EKCalendarStoreBackingStore _expandEventRangePredicate:countsOnly:]_block_invoke_3 + 679
25 libdispatch.dylib 0x00007fff5cec563d _dispatch_client_callout + 8
26 libdispatch.dylib 0x00007fff5ced1478 _dispatch_sync_invoke_and_complete_recurse + 65
27 libdispatch.dylib 0x00007fff5ced0fe6 _dispatch_sync_f_slow + 195
28 com.apple.ical.EventKit 0x00007fff3315d3b1 -[EKBackingStoreAccounting _accountForObjectCheckBlock:lookupCachedBlock:fetchContainersBlock:fetchObjectsBlock:
-
If anyone is looking for the reply it is not good. As I have many calendars over iCloud and they will just repopulate.
Shame developer cannot add a simple check for nil and repost the software.
On Oct 21, 2019, at 9:48 AM, On-Core Software Support <support@on-core.com> wrote:
Hi Brett,
I had something similar happen a long time back. It sounds like you have a corrupt Calendar (or Reminders) entry. It says it has a nil component in a record. Although this is a pain in the butt, this is how I determined what it was. I did a Full backup of the Calendar file. Then I deleted 1/2 of the file. Loaded up that and then see if it crashes (easiest to work on editing the file rather than deleting entries one-by-one in the calendar itself). If so, keep deleting 1/2 until it no longer crashes. Once you find the offending entry, then edit the original backup file and remove that one entry. It should then work after that.
Cheers,
Adam.