Saltheart

Q: Finder non-responsive, repeated coreduetd crashe

i have MacMini 2009 (early) that after running Yosemite well for about a month has recently had continuous issues with the Finder.  The Finder is non-responsive and relaunching does not have any apparent effects.  The console log shows repeated crashes of com.apple.launchd and com.apple.coreduted.  Activity Monitor shows that the Finder is non-responsive and intermittently Spotlight will also be non-responsive.

Other applications work but are significantly slower than normal.  I have booted into repair mode and ran Disk Utility followed by a reinstall of Yosemite.

 

ANy suggestions or things I have missed?

Mac mini, OS X Yosemite (10.10)

Posted on Nov 2, 2014 11:53 AM

Close

Q: Finder non-responsive, repeated coreduetd crashe

  • All replies
  • Helpful answers

Previous Page 2
  • by Saltheart,

    Saltheart Saltheart Nov 5, 2014 4:29 PM in response to Saltheart
    Level 1 (0 points)
    Nov 5, 2014 4:29 PM in response to Saltheart

    Please note I have Yosemite installed on an external drive and I am well aware of the failing internal SATA drive.  I'm also beginning to think that Cocktail is the root of the problem

  • by Linc Davis,

    Linc Davis Linc Davis Nov 5, 2014 5:43 PM in response to Saltheart
    Level 10 (208,000 points)
    Applications
    Nov 5, 2014 5:43 PM in response to Saltheart

    A.

     

    The failing internal hard drive may affect system stability, even if you're not using it.

     

    B.

     

    Remove "TechTool" and "Cocktail," neither of which serves any purpose.

    Any third-party software that doesn't install by drag-and-drop into the Applications folder, and uninstall by drag-and-drop to the Trash, is a system modification.

    Whenever you remove system modifications, they must be removed completely, and the only way to do that is to use the uninstallation tool, if any, provided by the developers, or to follow their instructions. If the software has been incompletely removed, you may have to re-download or even reinstall it in order to finish the job.

    I never install system modifications myself, and except as stated in this comment, I don't know how to uninstall them. You'll have to do your own research to find that information.

    Here are some general guidelines to get you started. Suppose you want to remove something called “BrickMyMac” (a hypothetical example.) First, consult the product's Help menu, if there is one, for instructions. Finding none there, look on the developer's website, say www.brickmymac.com. (That may not be the actual name of the site; if necessary, search the Web for the product name.) If you don’t find anything on the website or in your search, contact the developer. While you're waiting for a response, download BrickMyMac.dmg and open it. There may be an application in there such as “Uninstall BrickMyMac.” If not, open “BrickMyMac.pkg” and look for an Uninstall button. The uninstaller might also be accessed by clicking the Customize button, if there is one.

    Back up all data before making any changes.

    You will generally have to restart the computer in order to complete an uninstallation. Until you do that, there may be no effect, or unpredictable effects.

    If you can’t remove software in any other way, you’ll have to erase and install OS X. Never install any third-party software unless you're sure you know how to uninstall it; otherwise you may create problems that are very hard to solve.

    Trying to remove complex system modifications by hunting for files by name often will not work and may make the problem worse. The same goes for "utilities" such as "AppCleaner" and the like that purport to remove software.

    C.

    Modifying the hosts file is not a good way to block web ads. It may affect network performance, but probably not the Finder.

    D.

    Quit "Dropbox" and see whether there's an improvement.

    E.

    Back up all data.

    Triple-click the line below on this page to select it, then copy the text to the Clipboard by pressing the key combination  command-C:

    ~/Library/Preferences

    In the Finder, select

              Go Go to Folder...

    from the menu bar and paste into the box that opens by pressing command-V. You won't see what you pasted because a line break is included. Press return. A folder named "Preferences" will open. Inside it you may find several files, each with a name beginning in "com.apple" and ending in a string of seven random letters and numbers; for example:

              com.apple.loginwindow.plist.BVaKG1k

              com.apple.spaces.plist.X9cHIyJ

    Those are only examples. The files you find (if any) will have similar, but different, names. Move each such item to the Trash.

    Open the subfolder named "ByHost" and do the same.

    Log out or restart the computer and test.

  • by Derek-b,

    Derek-b Derek-b Jan 30, 2015 9:01 AM in response to Linc Davis
    Level 1 (0 points)
    Jan 30, 2015 9:01 AM in response to Linc Davis

    Hi there,

     

    I had a similar problem on my iMac 21" - running Yosemite 10.10.2.  After scouring around for solutions, I was going down the route described partly here and elsewhere of making a copy of coreduetd.db, dumping the contents and making a new copy and then importing the contents, and you get a clean data base. 


    Having done this in a working folder I was about to copy the new version (which according to Valentina Studio db manager, is now error free).  I noted that my new version was pretty well half the size of the current working version (although with the same number of tables and fields, which is good).


    I did my "usual" safe route of making another copy of coreduetd.db in the working folder (/var/db/CoreDuet/coreduetd.db) by renaming it (in this case to coreduetd_old.db).  The instant I did this a a new copy of coreduetd.db appeared!  Guess what, it was the same size as the "cleaned up" version I had just made.  Problem cured, no issues...


    So the simple solution for me is; rename the working copy of coreduetd.db (which is also now a copy you could go back to if required) and the OS automatically generates a new one, without errors!

     

    Cheers, Derek

Previous Page 2