Home > Default > Random Applications "quit unexpectedly" with EXC_BAD_ACCESS (SIGSEGV)

Random Applications "quit unexpectedly" with EXC_BAD_ACCESS (SIGSEGV)

November 30Hits:0
Advertisement
Hello! I have a Mid-2011 MacBook Air i7 1.8GHz, 256GB SSD. For a while now, I seem to have random applications crashing. Two that seem to trigger it a lot are Disk Utility, and going to About This Mac > More Info > Storage. Doing both of these about 80% of the time cause an immediate application crash.
I brought my Air into the Apple store to get this fixed, as I had already tried a complete Mountain Lion reinstall. They went ahead and replaced my logic board, but I'm still getting it.
Has anyone else been experiencing this on this type of machine? Or should I go back again?

Answers

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
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Enter the name of the crashed application or process in the Filter text field. Select the messages from the time of the last crash, if any. Copy them to the Clipboard (command-C). Paste into a reply to this message (command-V).
When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Important: Some private information, such as your name, may appear in the log. Anonymize before posting.
Step 2
Still in the Console window, look under User Diagnostic Reports for crash reports related to the process. The report name starts with the name of the crashed process, and ends with ".crash". Select the most recent report and post the entire contents — again, the text, not a screenshot. 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 shutdownStall, spin, or hang logs — they're very long and not helpful.

Read other 8 answers

Tags:

Related Articles

Copyright (C) 2019 wisumpire.com, All Rights Reserved. webmaster#wisumpire.com 14 q. 0.744 s.