Q: OS X Mavericks: Finder closes and restarts

So, a fix and apologies from Goolge The fix seems to have solved the issue here. Thanks, Google!

Fix posted by Google solved the issue for me. After posting it they've recommended closing GD and opening (or restarting the computer) to load the fix. I've turned-on the "Show sync status..." option just now and all seems to be running nice and easy again.

Cheers!

@Laario, I understand that, but if Mavericks has the same architecture as say Lion and ML, then why does the app behave erractically? Dont you think there is something in Mavericks that isnt working properly (with regards to the kernel)? Do you have Mavericks installed on your computer? Do you have first hand experience with upgrading to recent releases of OSX and how stability usually starts at 50% with the them? It wasnt like this before, believe me, it seems like their focus has shifted from stability to shiny features, that "showing of the desktop by itself" is a feature of Mavericks, not Google Drive, the code wasnt designed for Mavericks, but I bet you this is just the beginning of multiple issues to come with it... but yeah, we all use the system differently and so a consumer might just say ah whatever it'll be fixed in a patch, but when you deploy a system to 300 computers and this happens then we'll see how the reaction changes.

Not to mention that this issue only appeared YESTERDAY for me, and I've had Mavericks since launch.

For those that have the "update" for Drive, what does the version number say?  I'm curious if THIS update changed the version number, unlike whatever some say Google did that caused this in the first place.

Laario,

I sort of felt mine was a dumb question

Now I've clicked on the right icon and everything is fine.

Thanks a lot!

Anita

@yavnehtechsupport: I agree there is a "mismatch" between Mavericks and the Google Drive app, but to me it shows this was caused by an overnight update or change in the Google Drive app overnight. I do have Mavericks, since it's launch, and had no issues with Google Drive running on Mavericks, where Finder was playing hide & seek, up to today.  Unfortunately, I have no Lion or ML machines available to test or compare.   I use my Macs in a business environment, albeit not at that large a scale as you are, but I'm as irritated as you are, when it comes to this kind of bugs.   However, today's update of Google Drive has fixed the issue. My current version, after a the restart about half an hour ago, is 1.12.5329.1887

@Anita: no worries Glad to hear you fixed it.

Now.. where's that Crow..  It seems Google has updated the app and NOT updated the version number.  The number posted by Laario is the same number as that on a list my brother and I were collaborating on (on Google Docs ironically) when he was preparing for the arrival of his new MBP.  That list was generated Oct 26 and updated not very recently but the version number is the same as I was looking at the first time we looked at the doc.

I too have been uterly frustrated by this... and in general by the manufacturers scoring cheap points against each other by pretending that they know everything about everything at the expense of the end users... they are all now, most definitely, as bad as each other!

Anyway, the problem of what appears to be the relaunching Finder can also be stopped by pausing Google Drive from syncing - I had thought the problem was also caused by Dropbox syncing, but that does not appear to cause the same issue.

Hope that helps someone.

Or... If one reads the whole thread they'll see that I posted a link to the Google forums where it's said that the update they made to the application has resolved the problem and one just needs to close GD and restart it.  That fix has been discussed on this last page here as well.

Hit the issue after installing Mavericks. Actually I had it REALLY BAD. To the point where it even was walking me through the setup assistant - that was scary.

More importantly it was crashing SO much I couldn't even open a finder window to remove stuff.

First thing I did I was disable google drive (was installed but never used it). Didn't fix it.

Booted into safe mode (which made the whole system work just fine), and went through and pulled out the finder plist. Also removed stuff from startup window in System prefs. Booted back to normal: still busted.

Noticed there were a few MacAppStore apps still booting and started closing them. When I quit "Price Drop Monitor" (an app for tracking Amazon price drops) and suddenly the crash loop stopped.

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. But holy crap was that not a great first run experience. I just got a new rMBP which is running Mavericks just fine. But if this had been my only system I'd have been pretty crazy. Not to mention some of the crappier aspects of Mavericks such as the loss of 3rd-party plugin support in Quicktime.

I had this same problem. I don't use Google Drive, but I used to use Dolly Drive. Removing the DollySpaceTools folder did the trick.

Startupdiskname/Library/Application Support/DollySpaceTools

(This was driving me nuts!)

BTW, Dolly Drive has a note on their support page that says they have an update that is Mavericks compatible. I did not have that update installed when I installed Mavericks.

And I was having this problem, too, traced to the Copy app (like Dropbox, a Cloud storage outfit). On the Copy support page, they have a notice up about finder crashes and this advice:

This command will clear your dynamic link editor cache.

Please try entering this command in Terminal:

sudo update_dyld_shared_cache -force

Then reboot.

Seems to work.

Mate I have had the same problem then eventually the computer would not start up. I found this video its fix my computer from a total melt down.http://youtu.be/reV-9dmBAMk

Google drive was the culprit here too. Thank you all for having this discussion and helping to solve my problem.