You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

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

93164 Author

Level 1

12 points

com.apple.dock.extra crash....

I had a kernel panic today, and I looked at my Console after rebooting. Then I noticed that Console was plastered with crash reports for com.apple.dock.extra:

It seems that iTunes, Reminder, Calendar, etc are causing this:

And here is the link to the content of each individual report (I could not post the crash report because "invalid characters" won't let me create this thread...) :

http://forums.macrumors.com/threads/com-apple-dock-extra-crash-help.1963950/

The detail for kernel panic is also on that link.

So what could be wrong? I already repaired permissions in Recovery Mode. And I booted into Safe Mode, and I still get the same error messages. I was just staring at Console, and new crash report just popped up...

Thanks in advance.

iMac, OS X Mountain Lion (10.8.5)

Posted on Mar 27, 2016 8:57 AM

37 replies

93164 Author

Level 1

12 points

Jun 7, 2016 2:58 PM in response to 93164

Does 12.4.1 fix this issue?

atomicat

Level 1

19 points

Jun 7, 2016 3:03 PM in response to 93164

No, it does not.

However, please don't feel that you need our input to test this for yourself. The same procedure as mentioned previously will fix the plug-in in future releases as well if it is a continuing issue.

Hope this helps.

shape

Level 1

19 points

Aug 17, 2016 12:46 AM in response to atomicat

Thanks so much for this! I first tried Eric Root's suggestions but the problem still persisted. After running these 2 commands in Terminal this error no longer appeared the past few times i rebooted, which is a first since just before i ran that iTunes 12.3.3.17 update 5 months ago. In ~/Library/Logs/Diagnostic Reports I've had crash reports for this file going back to 3-30-16.

It's ridiculous Apple didn't fix this bug in a newer iTunes update.

CMRM

Level 1

25 points

Aug 31, 2016 9:53 AM in response to 93164

Oh joy! I've been having worsening problems for a while and nothing I tried worked. Then I found the suggestions here under "For those not wanting to go through the detailed version, here's a fast way to fix the problem:" and -- viola! It's like having a brand new computer. Oh happy day!