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

com.apple.dock.extra quit unexpectedly

After I updated iTunes to 12.3.3.17 today I immediately started to get this weird error message "com.apple.dock.extra quit unexpectedly" along with a long explanation or details that I (of course) could not understand!

Has anyone experienced this?

Any advice how to resolve this?

MacBook, OS X Mountain Lion (10.8.5)

Posted on Mar 23, 2016 7:15 AM

Reply
30 replies

Mar 30, 2016 11:28 AM in response to ammoun

Since Apple isn't likely to fix this issue any time soon AND I really don't have the time to create a whole new user account, I simply decided to disable the crash report pop up (since the Dock itself appears to be working). If you want to go this route do this:


Those that don’t like to wait every time an application crashes can disable the crash reporter with OS X Terminal. Just open Terminal (Applications > Utilities > Terminal) and type the following command:


defaults write com.apple.CrashReporter DialogType none


To enable crash reporter again use the following command:


defaults write com.apple.CrashReporter DialogType crashreport

Apr 3, 2016 7:35 PM in response to ammoun

https://discussions.apple.com/thread/7510129?answerId=30018357022#30018357022


It's a bug in the iTunesDockTile.docktileplugin from a recent update of iTunes.


I disabled the plugin and the crashes stopped.


In terminal:


sudo cp -rp "/Applications/iTunes.app/Contents/PlugIns" "/Applications/iTunes.app/Contents/PlugIns.bak"

sudo rm -rf "/Applications/iTunes.app/Contents/PlugIns/iTunesDockTile.docktileplugin"


Hope this helps.

Apr 22, 2016 7:05 PM in response to ammoun

I have exactly the same problem reported by ammoun, running the same OS 10.8.5 and I also JUST — against my better judgement [it ***** that I can no longer trust Apple upgrades!😠] — upgraded by iTunes to 12.3.3.17, and like him noticed the correlation. I suggest that most of the other advice has been issued without considering these circumstances, which now appear to me to imply cause and effect.


So, APPLE. jump right in and offer some solution to this. Is it critical? Is it possible to go back to my older iTunes [not the prior version as I have not been upgrading for some time, not willing to entrust my large and delicate iTunes library to sloppy new software]??

Apr 23, 2016 8:18 AM in response to whappen'd?

I'm not going to wait for Apple to fix this problem because, quite frankly, we're using an OS that is no longer supported by Apple and they want us to shift to El Capitan or the one that follows it. I also don't want to delete files and hope that those particular files rebuild themselves, nor do I want to create a new User account. So, using Terminal to stop the Crash Reporter was the solution that worked for me. Honestly, the only application that ever quits on me is Firefox...and I kinda don't need the Crash Reporter to tell me that it's stopped working.


Moral of the story: either upgrade to El Capitan or choose one of the solutions recommended above, 'cause I don't think Apple is listening to us.

Apr 23, 2016 12:21 PM in response to annehweb

The mantra here is that Apple reads but does not respond to discussions.


That being said, the problem is that the iTunes plug-in is crashing on 10.8.x due to what looks like a problem with the standard system run-time libraries. While 10.8 is no-longer supported, it would be fairly easy for Apple to fix the behavior in the iTunes plug-in with the next iTunes release. It's very likely, due to the widespread reports of this issue, that Apple is aware of the problem and will fix it in a subsequent iTunes update.


You have to remember that iTunes makes up about 20% of the code and frameworks in the OS, and while 10.8 may not be getting additional updates, iTunes will, far into the future, as it is tied to the iTunes store and iDevice management which are huge revenue streams to Apple and merit the continued support, even on 10.8.


Back to the issue: my method of disabling the plug-in stops the crash, and leaves your system in an otherwise unaltered state. When the next iteration of iTunes rolls, any newer plug-in code will be installed and hopefully fix the issue.


Hope this helps.

May 15, 2016 12:26 PM in response to Eric Root

Hi Eric:


com.apple.dock.extra is always using "significant energy."

Any suggestions on how I might determine why com.apple.dock.extra is showing up as an energy hog and whether I should do something about it?

Activity monitor doesn't break out the amount of energy being used for com.apple.dock.extra, but I'm assuming it's a real drain.

I was thinking about deleting the .plist pursuant to your directions, above.

Is there any reason to think this would be helpful?





Mid-2015 MacBook Pro Retina 15" w/ AMD Radeon R9 M370X 2048 MB

running: 10.11.4

com.apple.dock.extra quit unexpectedly

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