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

User profile for user: Oilersfan1
Oilersfan1 Author
User level: Level 1
0 points

calendar app keeps crashing despite restoring previous files

Hi everyone, desperate here and open to any suggestions.


Have a MacBook Pro (13-inch, Early 2011) operating on Yosemite OS X 10.10.5


Calendar crashed about a week ago. Thought it was a one time thing, but identical issues have happened since.

Every time I open it, is completely fine initially. I can actually scroll through months on the trackpad, etc.

However, whenever I then select a date, any date, to add or edit an event, the pinwheel starts going, it freezes and crashes.


Message is:

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000


Application Specific Information:

*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[CalUIInspectorPopoverController shouldDelayTrackingEventSelectionUntilEditing]: unrecognized selector sent to instance 0x60800034be70'

terminating with uncaught exception of type NSException

abort() called


I have followed instructions on previous threads to no avail.

Deleted caches and preferences.

Moved calendar to desktop. As per another thread, when I tried to relaunch it, it did open, suggesting that the app was corrupted.

I then went back a month on my Time Machine (when I know it was working well) and restored the Calendars folder, and re-opened it with identical results.


Any suggestions would be greatly appreciated.


Thanks!

MacBook Pro, OS X Yosemite (10.10.5)

Posted on Sep 1, 2015 5:40 PM

Reply
8 replies
User profile for user: Linc Davis
Linc Davis
User level: Level 10
209,547 points

Sep 1, 2015 7:17 PM in response to Oilersfan1

Launch the Console application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ Open LaunchPad and start typing the name.

Step 1

For this step, the title of the Console window should be All Messages. If it isn't, select

SYSTEM LOG QUERIES ▹ All Messages

from the log list on the left. If you don't see that list, select

View ▹ Show Log List

from the menu bar at the top of the screen.

In the top right corner of the Console window, there's a search box labeled Filter. Enter the name of the crashed application or process. For example, if Safari crashed, you would enter "Safari" (without the quotes.)

Each message in the log begins with the date and time when it was entered. Select the messages from the time of the last crash, if any. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.

The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.

Please don't indiscriminately dump thousands of lines from the log into this discussion.

Please don't post screenshots of log messages—post the text.

Some private information, such as your name, may appear in the log. Anonymize before posting.

Step 2

In the Console window, select

DIAGNOSTIC AND USAGE INFORMATION ▹ User Diagnostic Reports

(not Diagnostic and Usage Messages) from the log list on the left. There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of crash reports. The name of each report starts with the name of the process, and ends with ".crash". Select the most recent report related to the process in question. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.

I know the report is long, maybe several hundred lines. Please post all of it anyway.

If you don't see any reports listed, but you know there was a crash, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.

In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)

Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.

When you post the log extract or the crash report, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the forum software. Please post the text on Pastebin, then post a link here to the page you created.

Reply
User profile for user: Oilersfan1
Oilersfan1 Author
User level: Level 1
0 points

Sep 1, 2015 9:11 PM in response to Linc Davis

Hi, thanks for the help


Date/Time: 2015-09-01 18:12:47.762 -0600
OS Version: Mac OS X 10.10.5 (14F27)
Report Version: 11
Anonymous UUID:



Time Awake Since Boot: 2000 seconds


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


Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000


Application Specific Information:

*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[CalUIInspectorPopoverController shouldDelayTrackingEventSelectionUntilEditing]: unrecognized selector sent to instance 0x60000015d900'

terminating with uncaught exception of type NSException

abort() called


pplication Specific Backtrace 1:

0 CoreFoundation 0x00007fff9004703c __exceptionPreprocess + 172

1 libobjc.A.dylib 0x00007fff8b6f976e objc_exception_throw + 43

2 CoreFoundation 0x00007fff9004a0ad -[NSObject(NSObject) doesNotRecognizeSelector:] + 205

3 CoreFoundation 0x00007fff8ff8fe24 ___forwarding___ + 1028

4 CoreFoundation 0x00007fff8ff8f998 _CF_forwarding_prep_0 + 120

5 CalendarUI 0x00007fff90323138 -[EKEventViewController setEvent:] + 1019

6 Calendar 0x0000000102988864 Calendar + 2000996

7 CoreFoundation 0x00007fff9000345c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12

8 CoreFoundation 0x00007fff8fef3634 _CFXNotificationPost + 3140

9 AppKit 0x00007fff8de1a16e _NSPopoverSendWillShowNotification + 115

10 AppKit 0x00007fff8d78755d -[NSPopover showRelativeToRect:ofView:preferredEdge:] + 1721

11 Calendar 0x0000000102988620 Calendar + 2000416

12 Calendar 0x0000000102907a46 Calendar + 1473094

13 Calendar 0x0000000102851283 Calendar + 725635

14 Calendar 0x000000010281204f Calendar + 467023

15 Calendar 0x00000001029488ea Calendar + 1738986

16 Calendar 0x0000000102931255 Calendar + 1643093

17 libdispatch.dylib 0x00007fff94a20323 _dispatch_call_block_and_release + 12

18 libdispatch.dylib 0x00007fff94a1bc13 _dispatch_client_callout + 8

19 libdispatch.dylib 0x00007fff94a27cbf _dispatch_main_queue_callback_4CF + 861

20 CoreFoundation 0x00007fff8ff9a3f9 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9

21 CoreFoundation 0x00007fff8ff5568f __CFRunLoopRun + 2159

22 CoreFoundation 0x00007fff8ff54bd8 CFRunLoopRunSpecific + 296

23 HIToolbox 0x00007fff907df56f RunCurrentEventLoopInMode + 235

24 HIToolbox 0x00007fff907df2ea ReceiveNextEventCommon + 431

25 HIToolbox 0x00007fff907df12b _BlockUntilNextEventMatchingListInModeWithFilter + 71

26 AppKit 0x00007fff8d57d8ab _DPSNextEvent + 978

27 AppKit 0x00007fff8d57ce58 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 346

28 AppKit 0x00007fff8d572af3 -[NSApplication run] + 594

29 AppKit 0x00007fff8d4ef244 NSApplicationMain + 1832

30 Calendar 0x00000001027a1e9e Calendar + 7838

31 libdyld.dylib 0x00007fff91c455c9 start + 1

32 ??? 0x0000000000000001 0x0 + 1


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

0 libsystem_kernel.dylib 0x00007fff8ec9a286 __pthread_kill + 10

1 libsystem_c.dylib 0x00007fff894589b3 abort + 129

2 libc++abi.dylib 0x00007fff90b27a21 abort_message + 257

3 libc++abi.dylib 0x00007fff90b4f9d1 default_terminate_handler() + 267

4 libobjc.A.dylib 0x00007fff8b6fd7d6 _objc_terminate() + 103

5 libc++abi.dylib 0x00007fff90b4d0a1 std::__terminate(void (*)()) + 8

6 libc++abi.dylib 0x00007fff90b4d113 std::terminate() + 51

7 libobjc.A.dylib 0x00007fff8b6fd5ff objc_terminate + 9

8 libdispatch.dylib 0x00007fff94a1bc27 _dispatch_client_callout + 28

9 libdispatch.dylib 0x00007fff94a27cbf _dispatch_main_queue_callback_4CF + 861

10 com.apple.CoreFoundation 0x00007fff8ff9a3f9 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9

11 com.apple.CoreFoundation 0x00007fff8ff5568f __CFRunLoopRun + 2159

12 com.apple.CoreFoundation 0x00007fff8ff54bd8 CFRunLoopRunSpecific + 296

13 com.apple.HIToolbox 0x00007fff907df56f RunCurrentEventLoopInMode + 235

14 com.apple.HIToolbox 0x00007fff907df2ea ReceiveNextEventCommon + 431

15 com.apple.HIToolbox 0x00007fff907df12b _BlockUntilNextEventMatchingListInModeWithFilter + 71

16 com.apple.AppKit 0x00007fff8d57d8ab _DPSNextEvent + 978

17 com.apple.AppKit 0x00007fff8d57ce58 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 346

18 com.apple.AppKit 0x00007fff8d572af3 -[NSApplication run] + 594

19 com.apple.AppKit 0x00007fff8d4ef244 NSApplicationMain + 1832

20 com.apple.iCal 0x00000001027a1e9e 0x1027a0000 + 7838

21 libdyld.dylib 0x00007fff91c455c9 start + 1

Reply
User profile for user: Grant Bennet-Alder
Grant Bennet-Alder
User level: Level 10
127,135 points

Sep 1, 2015 9:31 PM in response to Oilersfan1

That is a very nice crash report. These do not tell much more to Readers that is not already in your first message.


But Linc Davis was asking for an extract of the System log > all messages. You have the exact date and time in this report. Now go back to his directions and pull out the console messages from about that time and post about a page from right about this time.

Reply

calendar app keeps crashing despite restoring previous files

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.
Learn more Sign up