Hi @tim.purdie,
We haven’t seen a Finder crash on High Sierra like the one you are describing. odrive may restart Finder to load the extensions, which could appear as a crash. Is it possible the Finder restart is being misinterpreted as a crash?
Other than that, there has been an obscure odrive crash (not Finder, though) that could happen because of malformed fsevents sent by MacOS when Apple registers for filesystem changes on external volumes. We were never able to pin that one down, although I haven’t seen a report of it for quite some time. If the external Volumes were removed the the crash would stop, so that is something that you could test to see if it makes a difference.
Before High Sierra there was a relatively easy way to disable fsevents before odrive started then re-enable them after, but that has since been locked down and rquires that you now disable “System Integration Protection” first. You can look here for more info on that workaround: O Drive Desktop Sync crashes after ~3-4 seconds (OSX) (with video)
As an alternative for testing/workaround, you can also take the odrive Finder extensions out of the equation by running this one-liner from the terminal:
o_ver_path="$HOME/.odrive/bin/$(ls -1 "$HOME/.odrive/bin/" | tail -n 1)";killall FinderSyncExtension -KILL; mv "$o_ver_path/odriveapp.app/Contents/PlugIns/FinderSyncExtension.appex" "$o_ver_path/odriveapp.app/Contents/PlugIns/FinderSyncExtension.appex.bak";
To reenable them:
o_ver_path="$HOME/.odrive/bin/$(ls -1 "$HOME/.odrive/bin/" | tail -n 1)";mv "$o_ver_path/odriveapp.app/Contents/PlugIns/FinderSyncExtension.appex.bak" "$o_ver_path/odriveapp.app/Contents/PlugIns/FinderSyncExtension.appex"