EXC_BAD_ACCESS KERN_INVALID_ADDRESS
Seen this lately on your Mac?
EXC_BAD_ACCESS (0x0001)
KERN_INVALID_ADDRESS (0x0001) at 0x67703000
I've seen it a couple of times, and it always gets the same reaction out of me. Holy shit! My hard drive is crashing!
Well, it may be, but more likely it means that a .plist file has become corrupt. People get these in many differnent applications. I won't go into why or how they easily become corrupted.
But there is a quick Solution (from your terminal window):
$> cd ~/Library/Preferences/ ... whatever application it is ... .plist
Find the application's .plist file that is offending and just delete it. Of course, you'll lose all your settings. For instance, if the corrupt file is from Mail (com.apple.mail.plist), then you'll lose your account settings, preferences, etc... it'll be like you installed Mail for the first time.
I'd recommend writing down all the options in your account you can get to before deleting the file.
EXC_BAD_ACCESS (0x0001)
KERN_INVALID_ADDRESS (0x0001) at 0x67703000
I've seen it a couple of times, and it always gets the same reaction out of me. Holy shit! My hard drive is crashing!
Well, it may be, but more likely it means that a .plist file has become corrupt. People get these in many differnent applications. I won't go into why or how they easily become corrupted.
But there is a quick Solution (from your terminal window):
$> cd ~/Library/Preferences/ ... whatever application it is ... .plist
Find the application's .plist file that is offending and just delete it. Of course, you'll lose all your settings. For instance, if the corrupt file is from Mail (com.apple.mail.plist), then you'll lose your account settings, preferences, etc... it'll be like you installed Mail for the first time.
I'd recommend writing down all the options in your account you can get to before deleting the file.
0 Comments:
Post a Comment
<< Home