MacOS: Saving to vault freezes cryptomator and hangs os #3085
Labels
Comments
|
i turned debug logs on and this is what it showed: 10:07:53.888 [Thread-33] WARN o.c.frontend.fuse.ReadOnlyAdapter - read /"folder"/"file" failed, invalid file handle 73 |
|
after cryptomator freezing, trying to browse vault: |
|
trying to lock vault (normally and forcefully) after it froze: |
Uj947nXmRqV2nRaWshKtHzTvckUUpD
changed the title
infeo
changed the title
infeo
changed the title
|
We tried to reproduce the problem with macOS 13.5.0 and fuse-t 1.0.27 but could not reproduce the issue. Will report back as soon as we updated our test system. @fusionneur Are you using an Intel or an M1 mac? And is you vault located on the local storage or at some cloud sync location? |
infeo
added
the
state:awaiting-response
|
Apple M1 Pro. vault is located on the local storage |
infeo
removed
the
state:awaiting-response
|
Apple M2 Pro. similar problem. I've installed fuse-t nothing change, unlock freeze os |
|
@blackout314 You also need to select FUSE-T in the general preferences. Is this the case? |
|
in my case it is selected |
2 tasks
|
in my case fuse-t selected |
|
I have same issue, macbook m1 pro, fuse-t selected, vault is in Goolge Drive disk (available offline selected) |
|
Are there any other logs we can provide? For me, the app is still unusable in the current state on Mac, as it breaks even when saving a text file in vscode, freezing both cryptomator and vscode. System cannot be rebooted afterwards as cryptomator needs to be closed to do that, but to close it requires locking the vault which doesn't work even forcefully. This results in having to long press the power button to power off the mac, and start it anew. Cryptomator latest version v1.10.1 |
|
@fusionneur, after the freeze
|
|
Hi @macos-fuse-t while waiting for @fusionneur I have some logs when it freezes on copying, only the copying is hanging, I still can tab out to other windows and typing it here: lan-mbp:ansible lan$ ps -ef | grep go-nfsv4 Killing it causes Finder hang, can be forced quit but can't re-open finder Hope this helps |
|
-78 mean the operation is not implemented. it's not an error, while the other one is also similarly missing functionality. you should look for other errors. I suggest filtering those out with " |
|
Here is the whole log file, I empty it before test run (before open cryptomator app) |
|
@ln8711 there's nothing in the logs to indicate a problem |
I took one last look on ps -ef and there were several umount attempts and umount -f At this point I attempted restart mac (reboot), which did nothing. But attempting to open random apps would not work anymore, dockbar freezing sometimes and the copying popup window to reappear. I also attempted shutdown but again did nothing other than popups like "you mac hasn't shut down because (eg.) terminal.app failed to quit. to continue shutting down, quit terminal.app. Attempted to force quit all open apps and pressed on the popup's retry (shutdown) button with no effect. More than half an hour passed, but couldn't recover or reboot so eventually turned mac off by power button long press (more than 5 sec or so)
What's worth noting is that when this happens, any app using files from mounted vault cannot be closed gracefully (in my case visual studio code, cryptomator, keepassxc), nor forcefully immediately, but only after closing the copying window they eventually force quit (or mabe after some timeout passed instead). Also, crpytomator vault cannot be locked, nor force locked anymore, not even waiting a lot of time, resulting in os unable to reboot/shutdown and having to press the power button to forcefully turn it off. later edit: ! after reboot, i found my files copied on the vault however, and having the exact size on disk as the original source, which is quite interesting |
|
I can see from the logs that fuse Read operation fails quite a lot. It happens on the app side so we need more insights from the Cryptomator guys. |
|
After debugging a similar issue with another Cryptomator user, I believe that I found a root cause. A new version with a fix is available to download |
|
As always, thank you, Alex! Out of curiosity, is this something that we could've/should've fixed on our side? |
is it fixed with: where can we see the commits / source code? |
Honestly I'm not sure, it was happening occasionally only on the user's machine with the similar errors to what was shared in this thread. I worked with the user who helped me to debug the issue. If I'll know more details, I'll share with you guys |
|
Last year cryptomator was crashing randomly on MacOS (Ventura). I didn't track to know exactly which update fixed it, but what i can tell is that it seems that these problems are not present anymore recently. REF on fuse-t macos-fuse-t/fuse-t#41 |
|
I am dealing with this now; I never got Fuse-T to work well on Mac with Cryptomator, but macFuse worked great. |
Are you sure? macFUSE still works for me. Where did you get this information? In the last macFUSE update, the release notes even stated increased compatibility with macOS 15. |
|
Ah! you're right. I hadn't updated MacFuse, and that's working great. Phew |
|
Hello. I think I'm affected by the same issue. I have always used fuse-t mainly because it installs and runs in userland so I avoided the tedious installation procedure for macfuse. However, it has always been rather unstable, locking up frequently. I took the instability as a trade-off for the convenience.
The logs refer to that folder and there are multiple errors: At this point I lost the data inside that folder. Is not recoverable. Fortunately I could recover a backup an update the changes. But this is very concerning. I use CM on my most valuable data so seeing this happen lowers my trust in it. |
|
fuse-t version: |
|
I understand that CM considers fuse-t experimental. From the time being I will use macfuse. |
|
Due to further problems with macOS 15, we are interested in the new SMB backend of FUSE-T for ARM Macs (M1 to M3 processors). First tests showed promising results, but we don't have the resources currently for extensive tests. If you want to help Cryptomator, switch to the SMB backend (described here: #3569 (comment)) and report your experience. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please agree to the following
Summary
critical bug - writing to disks freezes cryptomator
What software is involved?
Might be related to #1878
Volume Type
None
Steps to Reproduce
copy a file into vault using finder
copy freezes
Expected Behavior
no freeze
Actual Behavior
cannot cancel operation
cryptomator and finder freezes
cannot quit cryptomator
cannot restart mac. can only hard poweroff laptop to resume normal functionality
Reproducibility
Intermittent, but it happens often
Relevant Log Output
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: