93164

Q: 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:

 

Screen Shot 2016-03-27 at 1.25.29 AM.png

 

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

 

Screen Shot 2016-03-27 at 1.22.25 AM.png

 

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

Close

Q: com.apple.dock.extra crash....

  • All replies
  • Helpful answers

Previous Page 2 of 3 last Next
  • by 93164,

    93164 93164 Mar 30, 2016 2:06 PM in response to NJHJR
    Level 1 (10 points)
    Mac OS X
    Mar 30, 2016 2:06 PM in response to NJHJR

    Thank you SO MUCH for being brave and trying this!

     

    I wanted to trash these files, but I was too afraid to actually do it... There are past threads from 2012 where Mac users complained high CPU usage from com.apple.dock.extra, and solution was to trash some files. I was hesitant to try it because deleting system files could possibly cause more damages...

     

    Again, thank you so much for posting the solution. I really appreciate it!

  • by 93164,

    93164 93164 Mar 30, 2016 2:09 PM in response to annehweb
    Level 1 (10 points)
    Mac OS X
    Mar 30, 2016 2:09 PM in response to annehweb

    Yeah, especially iTunes updates are few and far between. Furthermore there is no guarantee that Apple will include the fix for this issue.... Thankfully, these crashes haven't at least affected computer usage.

     

    I am shocked by how iTunes update can damage Dock-related system file...

  • by etresoft,

    etresoft etresoft Mar 30, 2016 3:55 PM in response to NJHJR
    Level 7 (29,051 points)
    Mar 30, 2016 3:55 PM in response to NJHJR

    Hello NJHJR,

    All you are really doing is corrupting your operating system. That will clear up the error but only because you have deleted that part of the operating system that was reporting the problem. This wouldn't even be possible on El Capitan.

     

    Deleting preference files is really not a good idea. It probably isn't going to break too much but it will also probably not have much effect. You would have to make sure to delete those files when the process that created them is not running. Otherwise, it will just re-create the same corrupt files.

  • by NJHJR,

    NJHJR NJHJR Mar 30, 2016 6:40 PM in response to 93164
    Level 1 (9 points)
    Mar 30, 2016 6:40 PM in response to 93164

    No problem man. I figured since I had a carbon copied backup of my hard drive, the worst that could happen would be me needing to restore back to the state it was in, with the popup and trying something new. Just glad the message stopped popping up, it got really annoying after the first few times. Glad I could help.

  • by NJHJR,

    NJHJR NJHJR Mar 30, 2016 7:14 PM in response to etresoft
    Level 1 (9 points)
    Mar 30, 2016 7:14 PM in response to etresoft

    I won't say you're wrong, but I respectfully disagree. I'm using Mountain Lion on two different devices (MBP & Mac Mini) and before I deleted anything on the MBP (device with the corrupted files) and before backing up my hard drive, I checked for those same files on the Mac Mini as I'm running the same OS on both devices and one of the first things I noticed was that one of the files responsible for the error was missing altogether from the MBP, but was present on the Mac Mini. Also, the MBP had three different variations of the com.apple.dock plist, one regular, and two with a bunch of numbers and letters behind them, which wasn't being shown as plist files btw because they were corrupted, while the Mac Mini only had one plist file. After deleting everything, only one of everything was rebuilt, meaning the corrupt files weren't recreated. I have edited four videos, and updated three apps, one which needed a computer restart to finish the process, since deleting those files and letting the OS rebuild them and I've yet to see the error message again, so I'm positive now after multiple restarts that the corrupted files won't be recreated. Plus, the dock works, iTunes works (which I believe brought the error after an update), all of my everyday apps work, everything went as planned in disk utility (Disk doesn't need to be repaired because everything is ok after verifying it and all Disk permissions were verified without the need for repair) and most importantly, my laptop is still running smoothly. When the error popped up, my device would lag and I'd get an occasional spinning beach ball, since deleting those files, I no longer get that lag nor the beach ball.

  • by etresoft,

    etresoft etresoft Mar 31, 2016 10:07 AM in response to NJHJR
    Level 7 (29,051 points)
    Mar 31, 2016 10:07 AM in response to NJHJR

    Hello again NJHJR,

    But you referenced about 5 distinct kinds of files, from user preferences to operating system executables. Some will be rebuilt automatically. But some are gone forever. It is like someone complaining about errors in Mail. If they delete the app, they won't get those errors anymore. But they also won't get their mail.

     

    There may be multiple issues that display the same apparent crashes and error messages. If someone reports problems with the dock and they have a 3rd party dock hacking app, the first step is always to remove the 3rd party software and see if that fixes the problem for that specific user. The fix may not apply for anyone else.

  • by NJHJR,

    NJHJR NJHJR Mar 31, 2016 2:13 PM in response to etresoft
    Level 1 (9 points)
    Mar 31, 2016 2:13 PM in response to etresoft

    You're definitely right about that, which is why I refused to call you wrong in my initial response. My end result isn't guaranteed for everyone. In my case, every single thing I deleted, was rebuilt; there wasn't anything deleted that didn't come back after the system restart. And because of that, and the fact that me and the OP is running the same exact OS, I assumed what worked for me would work for him.

     

    Advice was already given to him from you to remove his third party dock app, and I assumed he tried that already and the issue still existed, so my advice was to be tried after following everything else mentioned before my response. If he took the advice from Eric Root, he should have everything backed up, so if anything goes wrong, he could simply restore back to it's current state and scratch it off as a fix if it didn't work out for him.

     

    I know my answer may not be the answer for everyone, but it was tested and worked flawlessly for me, so I'm just offering a way. He doesn't have to do it my way, but if he's as desperate and/or as annoyed as I was, then there's nothing to lose with everything already backed up.

  • by atomicat,Helpful

    atomicat atomicat Apr 3, 2016 8:16 PM in response to 93164
    Level 1 (19 points)
    Apr 3, 2016 8:16 PM in response to 93164

    com.apple.dock.extra.peer.0x7fca8b4193a0.xpcq c... | Apple Support Communities

     

    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.

  • by 93164,

    93164 93164 Apr 3, 2016 8:16 PM in response to etresoft
    Level 1 (10 points)
    Mac OS X
    Apr 3, 2016 8:16 PM in response to etresoft

    It is not Hyperdock. Like I said, it the error messages persisted in a new account. And another member from a different thread com.apple.dock.extra quit unexpectedly said he/she doesn't have anything like Hyperdock.

     

    I wonder why this crash only happened to Mountain Lion though.

  • by 93164,

    93164 93164 Apr 3, 2016 8:17 PM in response to atomicat
    Level 1 (10 points)
    Mac OS X
    Apr 3, 2016 8:17 PM in response to atomicat

    Thanks for posting this! I really appreciate it.

  • by makey,

    makey makey Apr 4, 2016 7:34 AM in response to Eric Root
    Level 1 (9 points)
    Desktops
    Apr 4, 2016 7:34 AM in response to Eric Root

    I've just stumbled upon this thread and I would like to say thank you very much for your Command-R Recovery suggestion, I've not had a recurrence of the annoying com.apple.dock.extra since following your advice.

  • by Eric Root,

    Eric Root Eric Root Apr 4, 2016 7:50 AM in response to makey
    Level 9 (69,813 points)
    iTunes
    Apr 4, 2016 7:50 AM in response to makey

    You are welcome.

  • by 93164,

    93164 93164 May 16, 2016 11:44 AM in response to 93164
    Level 1 (10 points)
    Mac OS X
    May 16, 2016 11:44 AM in response to 93164

    Does 12.4 update fix this issue?

  • by 93164,

    93164 93164 May 17, 2016 9:27 AM in response to 93164
    Level 1 (10 points)
    Mac OS X
    May 17, 2016 9:27 AM in response to 93164

    Or does the update damage other system files...?

  • by atomicat,

    atomicat atomicat May 18, 2016 9:26 AM in response to 93164
    Level 1 (19 points)
    May 18, 2016 9:26 AM in response to 93164

    > Does 12.4 update fix this issue?

     

    It does not, unfortunately.

     

    Hope this helps.

Previous Page 2 of 3 last Next