Benigumo

Q: com.apple.dock.extra.peer.0x7fca8b4193a0.xpcq crashing

No changes to my macbook pro until last week when I took the latest itune patch release and now I get the following crashes

 

Process:     com.apple.dock.extra [463]
Path:        /System/Library/CoreServices/Dock.app/Contents/XPCServices/com.apple.dock.extra. xpc/Contents/MacOS/com.apple.dock.extra
Identifier:  com.apple.dock.extra
Version:     1.0 (1)
Build Info:  Dock-1168009000000000~1
Code Type:   X86-64 (Native)

Parent Process:  ??? [1]

User ID:     502

 

Date/Time:   2016-03-27 14:37:28.576 -0400
OS Version:  Mac OS X 10.8.5 (12F2560)

Report Version:  10

 

Interval Since Last Report:      13853 sec
Crashes Since Last Report:       8

Per-App Interval Since Last Report:  13804 sec

Per-App Crashes Since Last Report:   8

Anonymous UUID:                  B76BC78E-B958-8D59-B27F-CA84186FA891

 

Crashed Thread:  0  Dispatch queue: com.apple.dock.extra.peer.0x7fae0201e750.xpcq

 

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000018

 

VM Regions Near 0x18:

-->

__TEXT             0000000106603000-0000000106608000 [   20K] r-x/rwx SM=COW  /System/Library/CoreServices/Dock.app/Contents/XPCServices/com.apple.dock.extra .xpc/Contents/MacOS/com.apple.dock.extra

 

Thread 0 Crashed:: Dispatch queue: com.apple.dock.extra.peer.0x7fae0201e750.xpcq

0   libobjc.A.dylib          0x00007fff8af8a498 objc_msgSend_vtable3 + 24
1   com.apple.Foundation     0x00007fff892fb2e7 -[NSBundle loadAndReturnError:] + 646
2   com.apple.Foundation     0x00007fff892fb05c -[NSBundle load] + 19
3   com.apple.Foundation     0x00007fff892fbc64 -[NSBundle principalClass] + 39
4   com.apple.dock.extra     0x0000000106604ecc 0x106603000 + 7884
5   com.apple.dock.extra     0x00000001066057c7 0x106603000 + 10183
6   libxpc.dylib             0x00007fff921394a2 _xpc_connection_recv_message + 699
7   libxpc.dylib             0x00007fff9213916d _xpc_connection_wakeup_recv + 165
8   libxpc.dylib             0x00007fff921378b4 _xpc_connection_wakeup2 + 1799
9   libxpc.dylib             0x00007fff9213717c _xpc_connection_wakeup + 145
10  libdispatch.dylib        0x00007fff8af6d0b6 _dispatch_client_callout + 8
11  libdispatch.dylib        0x00007fff8af6f29b _dispatch_source_invoke + 691
12  libdispatch.dylib        0x00007fff8af6e305 _dispatch_queue_invoke + 72
13  libdispatch.dylib        0x00007fff8af6e448 _dispatch_queue_drain + 180
14  libdispatch.dylib        0x00007fff8af6e2f1 _dispatch_queue_invoke + 52
15  libdispatch.dylib        0x00007fff8af72091 _dispatch_main_queue_callback_4CF + 220
16  com.apple.CoreFoundation 0x00007fff896f4b4c __CFRunLoopRun + 1644
17  com.apple.CoreFoundation 0x00007fff896f40e2 CFRunLoopRunSpecific + 290
18  com.apple.HIToolbox      0x00007fff8b477eb4 RunCurrentEventLoopInMode + 209
19  com.apple.HIToolbox      0x00007fff8b477c52 ReceiveNextEventCommon + 356
20  com.apple.HIToolbox      0x00007fff8b477ae3 BlockUntilNextEventMatchingListInMode + 62
21  com.apple.AppKit         0x00007fff8f61a533 _DPSNextEvent + 685
22  com.apple.AppKit         0x00007fff8f619df2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
23  com.apple.AppKit         0x00007fff8f6111a3 -[NSApplication run] + 517
24  com.apple.AppKit         0x00007fff8f5b5bd6 NSApplicationMain + 869
25  com.apple.XPCService     0x00007fff8f3b6d15 xpc_service_main + 433
26  com.apple.dock.extra     0x0000000106604744 0x106603

MacBook Pro (17-inch Early 2011), OS X Mountain Lion (10.8.5)

Posted on Mar 27, 2016 11:40 AM

Close

Q: com.apple.dock.extra.peer.0x7fca8b4193a0.xpcq crashing

  • All replies
  • Helpful answers

  • by Linc Davis,

    Linc Davis Linc Davis Mar 27, 2016 3:10 PM in response to Benigumo
    Level 10 (207,926 points)
    Applications
    Mar 27, 2016 3:10 PM in response to Benigumo

    Please post the rest of the crash report.

  • by atomicat,

    atomicat atomicat Apr 2, 2016 12:03 PM in response to Benigumo
    Level 1 (19 points)
    Apr 2, 2016 12:03 PM in response to Benigumo

    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 PenelopeTM,

    PenelopeTM PenelopeTM Apr 10, 2016 3:49 PM in response to atomicat
    Level 1 (4 points)
    Mac OS X
    Apr 10, 2016 3:49 PM in response to atomicat

    Thank you atomicat. This is exactly what my problem is. The crash reports started right after I tried to update iTunes.

    Except I have no idea what those 2 lines of data are and how you disabled the plugin. Can you break it down for me?

  • by atomicat,

    atomicat atomicat Apr 11, 2016 9:13 AM in response to PenelopeTM
    Level 1 (19 points)
    Apr 11, 2016 9:13 AM in response to PenelopeTM

    Hi PenelopeTM,

     

    The two lines I mentioned are to be copied and pasted into a terminal window. The first line (cp -rp) creates a copy of the PlugIn directory in case you want to move the buggy plug-in back later, and the second one (rm- rf) removes the plugin package from the disk. The terminal application is in the "Utilities" folder inside of the "Applications" folder on your hard disk. It presents you with a text-based interface for working with the system.

     

    Sudo is a Unix command (MacOS is Unix), that runs the command as the highest-privilege user (root), which is the user that owns the files you are changing. This is part of the Mac/Unix security model that most files on the system are not owned by the user running on the Desktop.

     

    Sudo will ask for your personal password when run to ensure that you are who you say you are and have the rights to elevate privileges to run the command. This means that the user running the command must be a user able to administer the computer (which is set in the Users and Groups control panel).

     

    This whole operation can be done from the Finder as well: Open the "Macintosh HD" from a finder window. Go into the "Applications" folder and find the iTunes application. Right-click on iTunes and select "Show package contents". Go into the "Contents" folder inside the finder window, highlight the PlugIns folder and right-click and select duplicate. You will need to enter your password on the dialog to make the copy. Once the copy is finished, go into the original "PlugIns" directory and move the "iTunesDockTile.docktileplugin" to the trash and empty the trash. You may need to provide your password to the security dialog again.

     

    As you can see, running the commands in the terminal application is much easier to do and fewer steps.

     

    Hope this helps.

  • by WZZZ,

    WZZZ WZZZ Apr 30, 2016 11:18 AM in response to atomicat
    Level 6 (13,087 points)
    Mac OS X
    Apr 30, 2016 11:18 AM in response to atomicat

    atomicat, had these Dock crashes, and incessant related error messages: Found your post, made a backup copy preserving permissions, and moved the plugin to the trash. Now seeing

     

    4/30/16 1:37:11.690 PM com.apple.dock.extra[311]: Could not load bundle for Dock Extra key iTunesDockTile.docktileplugin

    4/30/16 1:37:11.691 PM Dock[183]: Failed to set up extra plugin. file://localhost/Applications/iTunes.app/ Failed to get plugin class.

     

    Waiting to see if the Dock crashes and log spamming stop completely (seems to have, for now, at least) but what are the consequences of not having this plugin available to iTunes 12.3.3 in 10.8.5?

  • by atomicat,

    atomicat atomicat Apr 30, 2016 11:27 AM in response to WZZZ
    Level 1 (19 points)
    Apr 30, 2016 11:27 AM in response to WZZZ

    "Waiting to see if the Dock crashes and log spamming stop completely (seems to have, for now, at least) but what are the consequences of not having this plugin available to iTunes 12.3.3 in 10.8.5?"

     

    Absolutely nothing critical. The Dock plug-in is responsible for registering the badge number and icon updates on the iTunes Dock icon. It's completely cosmetic and if iTunes is logging an error, it's due to the program explicitly looking for the plug-in to load and not finding it. This is squarely in the realm of developers and the message is meant to tell Apple that something is wrong with the deployment should the logs be submitted to them.

     

    It's very likely that Apple already knows about the Dock crash due to the widespread reporting of this issue and will fix it in a subsequent iTunes update. At install-time, the new iTunes should deploy the new plug-in code and all will be well again.

     

    Hope this helps.

  • by WZZZ,

    WZZZ WZZZ Apr 30, 2016 5:23 PM in response to atomicat
    Level 6 (13,087 points)
    Mac OS X
    Apr 30, 2016 5:23 PM in response to atomicat

    The Dock plug-in is responsible for registering the badge number and icon updates on the iTunes Dock icon.

     

    Thanks for the solution and for getting back with an explanation of what this iTunes Dock plugin is for. Except for Mail, I have Notifications disabled, so won't miss any that junk.

     

    But, besides the Dock crashes (they were never noticeable, except in the logs) puzzled that the logs were also being relentlessly spammed by these other messages, which have nothing to do with iTunes.

     

    4/30/16 9:35:29.027 AM Dock[4300]: DockTilePlugin for application file://localhost/Applications/iTunes.app/ has failed. Trying again in 8 seconds

    4/30/16 9:35:29.029 AM Dock[4300]: DockTilePlugin for application file://localhost/Applications/System%20Preferences.app/ has failed. Trying again in 8 seconds

    4/30/16 9:35:29.029 AM Dock[4300]: connection to extra for file://localhost/Applications/System%20Preferences.app/ interrupted

    4/30/16 9:35:29.029 AM Dock[4300]: DockTilePlugin for application file://localhost/Applications/Reminders.app/ has failed. Trying again in 8 seconds

    4/30/16 9:35:29.030 AM Dock[4300]: connection to extra for file://localhost/Applications/Reminders.app/ interrupted

    4/30/16 9:35:29.031 AM Dock[4300]: DockTilePlugin for application file://localhost/Applications/Messages.app/ has failed. Trying again in 8 seconds

    4/30/16 9:35:29.031 AM Dock[4300]: connection to extra for file://localhost/Applications/Messages.app/ interrupted

    4/30/16 9:35:29.032 AM Dock[4300]: DockTilePlugin for application file://localhost/Applications/Calendar.app/ has failed. Trying again in 8 seconds

    4/30/16 9:35:29.032 AM Dock[4300]: connection to extra for file://localhost/Applications/Calendar.app/ interrupted

    4/30/16 9:35:29.033 AM Dock[4300]: DockTilePlugin for application file://localhost/Applications/FaceTime.app/ has failed. Trying again in 8 seconds

    4/30/16 9:35:29.033 AM Dock[4300]: connection to extra for file://localhost/Applications/FaceTime.app/ interrupted

    4/30/16 9:35:29.033 AM Dock[4300]: DockTilePlugin for application file://localhost/Applications/App%20Store.app/ has failed. Trying again in 8 seconds

  • by WZZZ,

    WZZZ WZZZ May 1, 2016 6:33 AM in response to WZZZ
    Level 6 (13,087 points)
    Mac OS X
    May 1, 2016 6:33 AM in response to WZZZ

    Interesting: with iTunes 12.3.3, on my 10.9, seeing none of these logs or Dock crashes. Not sure why it would matter, but perhaps because I have cDock installed there. Or maybe this bug is only affecting certain OSs.

  • by Ruthmike,

    Ruthmike Ruthmike May 11, 2016 11:26 AM in response to atomicat
    Level 1 (4 points)
    May 11, 2016 11:26 AM in response to atomicat

    This absolutely worked - Thanks

     

    So will the bug with the iTunesDockTile.docktileplugin be corrected by Apple in a future update?