Jump to content

Numerous crashes since forced migration to Google Drive for Desktop on OSX Mojave 10.14.6

Recommended Posts


I've had numerous crashes since forced migration to Google Drive for Desktop on or around July 12, 2021 which deprecated both Google FileStream and Google Backup and Sync.  Files are accessible via finder so that I do not have to utilize Google Drive via a browser.

Any time Affinity Designer has to access files that reside on Google Drive for Desktop, there has been an insane amount of crashes.  Could be while opening from the open dialog, saving from the saving dialog, exporting from the export dialog, etc.  It doesnt always happen but the behavior started with the Google Drive for Desktop update.  

Doesn't matter if it's a new document or an old one.

The same files, when previously accessed via the dialogs on files/folders that were FileStream or Backup and Sync have had no issues for as long as I can remember.

Have uninstalled and reinstalled Affinity Designer to no avail

Crash log is attached


Problem Report For Affinity Designer.rtf

Link to comment
Share on other sites

  • Staff

Hi @AdamB,

From checking the logs, the path for the app doesn't look like what we would normally see:
/Volumes/VOLUME/*/Affinity Designer.app/Contents/MacOS/Affinity Designer

Where is Designer stored on your Mac, eg external hard drive, cloud drive even?  Also both, crashes appear to related to Fonts, are you using any other font manager apart from FontBook?

So far, this doesn't appear to be related to the Google Drive side of things but we have always recommended not working directly from Cloud services or network locations, as it has been known to cause problems and lead to corrupt files.

Link to comment
Share on other sites

Thank you for your insight, @stokerg.

Looks like Designer was running off of a system backup somehow.  I've uninstalled that and reinstalled to the normal location.

Also, Font Book has been giving me a lot of problems since the Google Drive update as well.  I'm sure this was because I was using a symbolic link to my Fonts folder which resided on Google Drive so that I can synchronize the fonts I use with my other computers.  I've since unlinked and restored Font Book to it's original form.  

I'll give this setup a go and see if the issue persists.   

Link to comment
Share on other sites

  • 3 months later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.