Cryptomator process gets stuck on macOS while locking the vault

archil · January 14, 2022, 2:40pm

Hello,

I am creating a new vault on macOS 12.1 and copying about 300GB files in it using rsync. After copy completes, everything looks okay. But when I try to lock the vault, I get an error that the vault is busy. If I click on retry, the Cryptomator process ID goes in stuck state, and on the GUI next to the vault the progress is rotating. Then I get some processes like finder/terminal completely stuck on my Mac and I need to restart.

This is a fresh installation of macOS Monterey and fresh installation of Cryptomator 1.6.5. The issue doesn’t happen on vaults with small amount of data. I don’t use MacFUSE just WebDav.

Best Regards,
Archil

infeo · January 17, 2022, 11:10am

This is a known issue, see

github.com/cryptomator/cryptomator

Application freezes after forced lock (M1 Mac, Big Sur, WebDAV)

opened 06:43AM - 07 Oct 21 UTC

MalEbenSo

type:bug os:mac mount:webdav state:has-workaround

### Please agree to the following - [X] I have searched [existing issues](https…://github.com/cryptomator/cryptomator/issues?q=) for duplicates - [X] I agree to follow this project's [Code of Conduct](https://github.com/cryptomator/cryptomator/blob/develop/.github/CODE_OF_CONDUCT.md) ### Summary When trying to quit Cryptomator while there are open files on the volume, Cryptomator will hang i. e. become unresponsive. ### What software is involved? - Operating System: macOS Big Sur 11.6 - Cryptomator: 1.5.19 (dmg-2838.133) - Mount method: WebDAV ### Volume Type WebDAV ### Steps to Reproduce 1. Mount a volume via WebDAV. 2. Open a file in the volume, e. g. a PDF document in Preview. I have found that just an open Finder window also triggers the problem. 3. Quit Cryptomator. 4. Cryptomator asks whether it should unmount and lock the volume. ### Expected Behavior Cryptomator returns an error message that unmounting and locking has failed because of open files. Ideally Cryptomator would also list the relevant files and / or apps. In any case the user can close open files and then try again. ### Actual Behavior Cryptomator hangs, i. e. becomes unresponsive. No error message. No quitting. No retry possible. In fact it can mess up the WebDAV side so badly, that the machine in total misbehaves, gets sluggish. In this state a restart of the OS is not possible without force quitting apps / processes or force restarting. ### Reproducibility Always ### Relevant Log Output _No response_ ### Anything else? Diligently make sure, that there are no open files on the volume and no Finder windows / tabs before quitting Cryptomator and / or unmounting the volume, locking the vault.

Unfortunately, there is no known workaround except using MacFUSE.

archil · January 17, 2022, 12:01pm

Using MacFUSE is not a good idea as it is not completely safe. It is touching the kernel of the operating system and can cause problems. Also it uses very old version of SSHFS.

Do you have any plan to find a solution without using MacFUSE?

infeo · January 17, 2022, 12:10pm

Yes. In the longer run, we want to use Apples FileProvider extenstion.

We are working towards it, but currently there is no ETA for it.