As the title states, Finder freezes/hangs when I try to access multiple files in a vault, at this point I have to force-unmount the vault in Cryptomator. There is a chance that some files can be accessed after re-mount, but when I access some new files it might freeze again.
Cryptomator on my Apple Silicon Macs is from the beginning a nightmare. pdf and Pages documents often cause problem, the Finder is freezing – only restarting my Mac helps. The problems have existed since the Apple Silicon chips have been around, they just change from time to time. It’s really weak that they can’t get this under control. I switch between fuse-t and Web DAV (Apple Script), but both keep causing problems. I’m really disappointed and do not have any solutions until now.
(Problems exist btw on different Macs: my M1 Mac Studio, my M2 Mac mini and my M1 MacBook Pro – all with latest macOS versions; my vault is located on my iCloud Drive.)
I have the same issue I narrowed it down to the OnDemand function of OneDrive for some reason if cryptomator tries to access a file that is not yet downloaded. OneDrive doesn’t start downloading. This causes the freeze. You can work around that by right click on the encrypted vault inside your One Drive and select to keep files on the computer. The sync feature of OneDrive is pretty poor on MacOS I am rather sure this is on purpose from Microsoft.
One month later all problems still exist (now for more than a year). The fuse-t version I am using is 0.38, Cryptomator is on 1.12.3.
But I noticed something on my Apple Silicon Macs: The problems with the freezing Finder and the inability to quit Cryptomator are happening when my Mac was sleeping. It seems that Cryptomator and fuse-t (but also when using WebDAV Apple Script) cannot handle it when my Mac was woken up after sleep mode.
Can anyone confirm that?
When there is no FUSE-T, I do use WebDAV, but it actually causes the exact same freeze issue if mounted via Finder.
I suspect this is a network-related deadlock issue. FUSE-T can’t solve this problem because it essentially mounts the filesystem using NFS, which is still network-based. I guess the network requests of OneDrive’s FileProvider (for downloading offloaded On-Demand files) and the loopback network requests of the network-based FS are waiting for each other, causing a deadlock. These codes may run at the kernel (extension) level, which is why reboot is forced sometimes.
I don’t think anyone other than Apple (and possibly Microsoft) can address the issue. Best solution will be mounting Vaults using the FileProvider API, but devs are apparently unwilling to implement this as corresponding GitHub issue has been stale for years.
As others have mentioned before, the best way for users to avoid this problem seems to be requesting OneDrive to always keep vault files locally, which does reduce the chance of Finder freezing, not a perfect fix as I still encounter the issue sometimes.
Same issue, Cryptomator on macOS 26.x is a nightmare and is blocking the reboot of the OS, the only way is to force macOS to reboot (that is very very very BAD)
17:43:15.125 [App Background Thread 006] INFO o.cryptomator.ui.lock.LockWorkflow - Locking Coffre_cryptomat failed (forced: false). org.cryptomator.integrations.mount.UnmountFailedException: java.util.concurrent.TimeoutException: umount timed out after 10s at org.cryptomator.frontend.fuse@5.0.5/org.cryptomator.frontend.fuse.mount.MacMountedVolume.unmount(MacMountedVolume.java:47) 17:44:40.762 [JavaFX Application Thread] INFO o.cryptomator.ui.fxapp.UpdateChecker - Current version: 1.17.1, latest version: 1.17.1 at org.cryptomator.desktop@1.17.1/org.cryptomator.ui.lock.LockWorkflow.lock(LockWorkflow.java:66) … 11 common frames omitted 17:43:02.036 [App Background Thread 006] INFO o.cryptomator.ui.lock.LockWorkflow - Locking Coffre_cryptomat failed (forced: false). 17:43:15.125 [App Background Thread 006] INFO o.cryptomator.ui.lock.LockWorkflow - Locking Coffre_cryptomat failed (forced: false). 17:44:40.762 [JavaFX Application Thread] INFO o.cryptomator.ui.fxapp.UpdateChecker - Current version: 1.17.1, latest version: 1.17.1 at org.cryptomator.desktop@1.17.1/org.cryptomator.common.vaults.Vault.lock(Vault.java:201) at org.cryptomator.desktop@1.17.1/org.cryptomator.ui.lock.LockWorkflow.lock(LockWorkflow.java:63) at org.cryptomator.desktop@1.17.1/org.cryptomator.ui.lock.LockWorkflow.call(LockWorkflow.java:57) at org.cryptomator.desktop@1.17.1/org.cryptomator.ui.lock.LockWorkflow.call(LockWorkflow.java:34) at javafx.graphics@24.0.1/javafx.concurrent.Task$TaskCallable.call(Unknown Source) at java.base/java.util.concurrent.FutureTask.run(Unknown Source) at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source) Caused by: java.util.concurrent.TimeoutException: umount timed out after 10s at org.cryptomator.frontend.fuse@5.0.5/org.cryptomator.frontend.fuse.mount.ProcessHelper.waitForSuccess(ProcessHelper.java:29) at org.cryptomator.frontend.fuse@5.0.5/org.cryptomator.frontend.fuse.mount.MacMountedVolume.unmount(MacMountedVolume.java:40) … 11 common frames omitted 17:43:02.036 [App Background Thread 006] INFO o.cryptomator.ui.lock.LockWorkflow - Locking Coffre_cryptomat failed (forced: false). org.cryptomator.integrations.mount.UnmountFailedException: java.util.concurrent.TimeoutException: umount timed out after 10s at org.cryptomator.frontend.fuse@5.0.5/org.cryptomator.frontend.fuse.mount.MacMountedVolume.unmount(MacMountedVolume.java:47) at org.cryptomator.frontend.fuse@5.0.5/org.cryptomator.frontend.fuse.mount.MacMountedVolume.unmount(MacMountedVolume.java:27) at org.cryptomator.desktop@1.17.1/org.cryptomator.common.vaults.Vault.lock(Vault.java:201) at org.cryptomator.desktop@1.17.1/org.cryptomator.ui.lock.LockWorkflow.lock(LockWorkflow.java:63) at org.cryptomator.desktop@1.17.1/org.cryptomator.ui.lock.LockWorkflow.retryOrCancel(LockWorkflow.java:73) at org.cryptomator.desktop@1.17.1/org.cryptomator.ui.lock.LockWorkflow.lock(LockWorkflow.java:66) at org.cryptomator.desktop@1.17.1/org.cryptomator.ui.lock.LockWorkflow.call(LockWorkflow.java:57) at org.cryptomator.desktop@1.17.1/org.cryptomator.ui.lock.LockWorkflow.call(LockWorkflow.java:34) at javafx.graphics@24.0.1/javafx.concurrent.Task$TaskCallable.call(Unknown Source) at java.base/java.util.concurrent.FutureTask.run(Unknown Source) at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source) Caused by: java.util.concurrent.TimeoutException: umount timed out after 10s at org.cryptomator.frontend.fuse@5.0.5/org.cryptomator.frontend.fuse.mount.ProcessHelper.waitForSuccess(ProcessHelper.java:29) at org.cryptomator.frontend.fuse@5.0.5/org.cryptomator.frontend.fuse.mount.MacMountedVolume.unmount(MacMountedVolume.java:40) … 13 common frames omitted 17:43:15.125 [App Background Thread 006] INFO o.cryptomator.ui.lock.LockWorkflow - Locking Coffre_cryptomat failed (forced: false). org.cryptomator.integrations.mount.UnmountFailedException: java.util.concurrent.TimeoutException: umount timed out after 10s at org.cryptomator.frontend.fuse@5.0.5/org.cryptomator.frontend.fuse.mount.MacMountedVolume.unmount(MacMountedVolume.java:47) at org.cryptomator.frontend.fuse@5.0.5/org.cryptomator.frontend.fuse.mount.MacMountedVolume.unmount(MacMountedVolume.java:27) at org.cryptomator.desktop@1.17.1/org.cryptomator.common.vaults.Vault.lock(Vault.java:201) at org.cryptomator.desktop@1.17.1/org.cryptomator.ui.lock.LockWorkflow.lock(LockWorkflow.java:63) at org.cryptomator.desktop@1.17.1/org.cryptomator.ui.lock.LockWorkflow.retryOrCancel(LockWorkflow.java:73) at org.cryptomator.desktop@1.17.1/org.cryptomator.ui.lock.LockWorkflow.lock(LockWorkflow.java:66) at org.cryptomator.desktop@1.17.1/org.cryptomator.ui.lock.LockWorkflow.retryOrCancel(LockWorkflow.java:73) at org.cryptomator.desktop@1.17.1/org.cryptomator.ui.lock.LockWorkflow.lock(LockWorkflow.java:66) at org.cryptomator.desktop@1.17.1/org.cryptomator.ui.lock.LockWorkflow.call(LockWorkflow.java:57) at org.cryptomator.desktop@1.17.1/org.cryptomator.ui.lock.LockWorkflow.call(LockWorkflow.java:34) at javafx.graphics@24.0.1/javafx.concurrent.Task$TaskCallable.call(Unknown Source) at java.base/java.util.concurrent.FutureTask.run(Unknown Source) at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source) Caused by: java.util.concurrent.TimeoutException: umount timed out after 10s at org.cryptomator.frontend.fuse@5.0.5/org.cryptomator.frontend.fuse.mount.ProcessHelper.waitForSuccess(ProcessHelper.java:29) at org.cryptomator.frontend.fuse@5.0.5/org.cryptomator.frontend.fuse.mount.MacMountedVolume.unmount(MacMountedVolume.java:40) … 15 common frames omitted 17:44:40.762 [JavaFX Application Thread] INFO o.cryptomator.ui.fxapp.UpdateChecker - Current version: 1.17.1, latest version: 1.17.1
I also had problems with Finder freezing when I updated to the latest FUSE-T version (1.0.49). I downgraded to 1.0.47 and the problem was fixed. My current configuration is: Macbook Air M3, CM 1.17.1, and FUSE 1.0.47 with MAC OS 15.7.2. I won’t update to Tahoe as long as everything works.