mhparkman

Q: Mavericks Finder keeps crashing!

Since upgrading to Mavericks the finder crashes. Pop up box appears briefly, doesn't not show drives or menu bar. Any suggestions?

MacBook Pro, OS X Mountain Lion (10.8.2)

Posted on Oct 23, 2013 1:02 PM

Close

Q: Mavericks Finder keeps crashing!

  • All replies
  • Helpful answers

first Previous Page 4 of 5 last Next
  • by squareman,

    squareman squareman Nov 6, 2013 12:11 PM in response to mhparkman
    Level 1 (34 points)
    iCloud
    Nov 6, 2013 12:11 PM in response to mhparkman

    Looks like Google has fixed the problem as of Nov 5. You need to get Google Drive updated if isn't already or restart Google Drive: https://productforums.google.com/forum/#!category-topic/drive/report-a-problem/k qdqmoMWtk8

  • by Alisa22,

    Alisa22 Alisa22 Nov 6, 2013 12:53 PM in response to ehmjay
    Level 1 (0 points)
    Nov 6, 2013 12:53 PM in response to ehmjay

    Thought it was totally fixed, but did get a bunch of crashes early this morning while showering, but the loop stopped before I noticed and seemed to be fine. So I went in and deleted all files in the Library/LaunchAgents, Library/LaunchDaemons and Library/StartupItems folders.

     

    So far everything seems fine.

     

    Is it safe to remove all those? And do you mean in User Library or System Library?

    I am one of those that does not have Google Drive so most of these suggestions are not working for me.

  • by Strathclyde1995,

    Strathclyde1995 Strathclyde1995 Jan 21, 2014 1:12 PM in response to mhparkman
    Level 1 (0 points)
    Jan 21, 2014 1:12 PM in response to mhparkman

    Finder is unusable!!!!!!!!!!! it crashes every 5 seconds, is unbearable. OS X ML, where are you???????? How can we solve this problem?

  • by roma86,

    roma86 roma86 Feb 2, 2014 3:26 AM in response to Strathclyde1995
    Level 1 (0 points)
    Feb 2, 2014 3:26 AM in response to Strathclyde1995

    Disable "show file sync status icons..." for google drive app solve this problem for me.

  • by Akihiro Yoshida,

    Akihiro Yoshida Akihiro Yoshida Feb 2, 2014 6:15 PM in response to mhparkman
    Level 1 (0 points)
    Feb 2, 2014 6:15 PM in response to mhparkman

    https://support.filetransporter.com/article/AA-00398

    I find that subject.maybe same problem?

  • by jdhovland,

    jdhovland jdhovland Feb 5, 2014 9:17 AM in response to mhparkman
    Level 1 (0 points)
    Feb 5, 2014 9:17 AM in response to mhparkman

    I just had this start happening to me on a Late 2013 15" Retina MBP, the finder wouldn't open new windows or tabs. The only way to open a finder window was from terminal using the "open ." command. I resolved it by going to the /User/Library/Preferences/ directory and removing the com.apple.finder.plist file entirely and then restarting the system. Prior to that I'd tried the disk repair utility, deleting the plist file and relaunching the finder from the force quit menu all to no avail. The delete of the plist file followed by an immediate restart solved the issue.

  • by peterskillen,

    peterskillen peterskillen Feb 14, 2014 8:48 AM in response to fwmaietta
    Level 1 (0 points)
    Feb 14, 2014 8:48 AM in response to fwmaietta

    This solution just worked for me too! :-) Thank you!

  • by jwl3v,

    jwl3v jwl3v Apr 29, 2014 1:37 PM in response to jdhovland
    Level 1 (20 points)
    Apr 29, 2014 1:37 PM in response to jdhovland

    jdhovland appears to have basically the right solution, at least for those who don't have Google drive installed.

    I, too, had completed a hierarchy of alternative solutions without success, but when I removed the plist and rebooted, that seems to have eliminated the problem of hangs. However, he's moving the system plist. I think one only has to move the specific user's plist.

     

    Option+Go to the Library and navigate to the preferences directory ("folder"); drag com.apple.finder.plist to the desktop (for safe keeping) and then restart.

     

    Alternatively, if the Finder is so unstable you can't use it, use Terminal and type

     

    ==> mv /User/[USERSHORTNAME]/Library/Preferences/com.apple.finder.plist /User/[USERSHORTNAME]/Desktop/.

     

    Then restart.

     

    If everything is then O.K., one can discard the (apparently corrupted) plist.

     

    The user will lose special settings associated with the Finder (e.g., customizations for the Finder toolbar). Those will have to be recreated.

  • by Toby Cockcroft,

    Toby Cockcroft Toby Cockcroft Jun 11, 2014 7:09 PM in response to LasseMartinell
    Level 3 (945 points)
    Jun 11, 2014 7:09 PM in response to LasseMartinell

    I'm running 10.9 and just started getting this issue.  It really just came out of the blue, however, I followed the directions concerning Google Drive and that seems to have cleared it up.

  • by webguide,

    webguide webguide Sep 10, 2014 12:56 AM in response to fwmaietta
    Level 1 (12 points)
    Apple TV
    Sep 10, 2014 12:56 AM in response to fwmaietta

    I closed Google drive so it was the problem. I have a problem with Googel drive so I will just deinstall it.

  • by julien119,

    julien119 julien119 Jan 28, 2015 3:00 AM in response to webguide
    Level 1 (0 points)
    Jan 28, 2015 3:00 AM in response to webguide

    Hello,

     

    I had exactly the same problem where I could not use the Finder any more because of multiple crashes. When I look into the crash reports in /Users/YOURNAME/Library/Logs/DiagnosticReports/ where YOURNAME is your user name, I found multiple crash related to a Synology plugin. So I uninstall Synology Cloud Station and everything went back to normal. To do so, I use AppCleaner. It's weird to see that 2 softwares doing the same thing (sharing files in the cloud) managed to crash the Finder in the same way.

     

    Here is part of Finder crash file:

     

    Process:               Finder [1586]

    Path:                  /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder

    Identifier:            com.apple.finder

    Version:               10.10.1 (10.10.1)

    Build Info:            Finder_FE-932001003000000~1

    Code Type:             X86-64 (Native)

    Parent Process:        ??? [1]

    Responsible:           Finder [1586]

    User ID:               501

     

    PlugIn Path:             /Users/USER/*/SynoMacIconOverlay.bundle/Contents/MacOS/SynoMacIconOverlay

    PlugIn Identifier:       synology.SynoMacIconOverlay

    PlugIn Version:          1.0 (1)

    OS Version:            Mac OS X 10.10.1 (14B25)

    Exception Type:        EXC_BAD_ACCESS (SIGSEGV)

    Exception Codes:       KERN_PROTECTION_FAILURE at 0x00007fff5e637ff8

     

    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

    0   synology.SynoMacIconOverlay   0x0000000106e45b24 -[NSObject(IconOverlay) SynoDrawRect:] + 65

    1   synology.SynoMacIconOverlay   0x0000000106e45b27 -[NSObject(IconOverlay) SynoDrawRect:] + 68

  • by iloveannie,

    iloveannie iloveannie May 28, 2015 3:17 AM in response to fwmaietta
    Level 1 (0 points)
    May 28, 2015 3:17 AM in response to fwmaietta

    Re-installed the OS yesterday, deleted a few files today, scratched my head, googled some more. Finally I read the part about Google Drive and so far it's been a few minutes and Finder hasn't crashed.

     

    Why is it normally always just a tick in a bloody box that causes so many problems? Bit like parliamentary elections

  • by KoenFromNL,

    KoenFromNL KoenFromNL Jul 16, 2015 7:51 AM in response to Dave Sag
    Level 1 (0 points)
    Jul 16, 2015 7:51 AM in response to Dave Sag

    Got the same here! Constant crashing of the Finder. After I quit Google Drive, it's all OK.

  • by totoantonio,

    totoantonio totoantonio Jul 28, 2015 7:55 PM in response to mhparkman
    Level 1 (0 points)
    Jul 28, 2015 7:55 PM in response to mhparkman

    Usually if this happens, below are my steps.

     

    Command + Option + Esc.

    Then select Finder

    Then Relaunch.

  • by noula,

    noula noula Aug 9, 2016 2:31 PM in response to julien119
    Level 1 (8 points)
    Aug 9, 2016 2:31 PM in response to julien119

    With older macs, it might be a memory problem. Run etrecheck, it'll tell you if that's so.

first Previous Page 4 of 5 last Next