Notes app on Yosemite crashing repeatedly

Question

Level 1

9 points

Notes app on Yosemite crashing repeatedly

Since installing Yosemite my Notes app has been behaving badly. At first many notes on Yosemite were empty but I could see the content on my iOS devices so I went in to the Apple Store (I was in the USA at the time) and they unconnected my Notes all from iCloud in Settings / Accounts then reconnected and that appeared to work because all notes were now complete (no blanks). But after leaving the Apple store I discovered that I cannot type into or paste into notes because it crashes the app and once it crashes once then it crashes over time I try to open it. I get big long error message. All I can do then is unconnected and reconnect with icloud which lets me in to Notes to read notes but I cannot edit or add. I am now back in Ireland where we have no Apple Store and I have tried everything I can find in these forums myself but nothing is working. Anybody got any ideas?

Patricia

Posted on Nov 20, 2014 10:15 AM

Reply

Answer 1

Linc Davis

Level 10

209,535 points

Nov 20, 2014 11:03 AM in response to patti_os

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. Click Utilities, then Console in the icon grid.

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. Initially the words "String Matching" are shown in that box. 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.

Reply

Answer 2

patti_os Author

Level 1

9 points

Nov 20, 2014 12:35 PM in response to Linc Davis

Thanks Linc for helping with this... here you go... the User Diagnostic reports are actually all very short as you will see below... Patricia

20/11/2014 8:13:47.331 p.m. Notes[8866]: (

0 CoreFoundation 0x00007fff9032064c __exceptionPreprocess + 172

1 libobjc.A.dylib 0x00007fff88d006de objc_exception_throw + 43

2 CoreFoundation 0x00007fff9032042a +[NSException raise:format:arguments:] + 106

3 Foundation 0x00007fff8c4bb5b9 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 195

4 Notes 0x00007fff91bc5729 -[NFIMAPFolder messageWithUniqueID:] + 416

5 IMAP 0x00007fff91e6ca20 __32-[IMAPMailboxProxy addMessages:]_block_invoke + 827

6 CoreData 0x00007fff87871a66 developerSubmittedBlockToNSManagedObjectContextPerform + 182

7 libdispatch.dylib 0x00007fff83921c13 _dispatch_client_callout + 8

8 libdispatch.dylib 0x00007fff83925365 _dispatch_queue_drain + 1100

9 libdispatch.dylib 0x00007fff83926ecc _dispatch_queue_invoke + 202

10 libdispatch.dylib 0x00007fff839246b7 _dispatch_root_queue_drain + 463

11 libdispatch.dylib 0x00007fff83932fe4 _dispatch_worker_thread3 + 91

12 libsystem_pthread.dylib 0x00007fff91dee6cb _pthread_wqthread + 729

13 libsystem_pthread.dylib 0x00007fff91dec4a1 start_wqthread + 13

)

20/11/2014 8:13:47.332 p.m. Notes[8866]: *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Got more than one note with UUID <__NSConcreteUUID 0x608000238d60> F5C59AAF-1C8E-42B1-A418-BCC93DC242B8'

*** First throw call stack:

(