notpeter
commented
5 days ago Zed is interfacing with that software only using the normal operating systems call for reading and writing files/directories on the filesystem. If it is crashes, it's more likely because it cannot actually handle a high volume of reads in parallel. Often times FUSE filesystems work great of low volume access but once you try to read/write multiple files simultaneously everything falls apart.
The fact that it worked in the past may have been a fluke or it could be an area where Zed now has improved parallelization seeking better performance. If you can track down a particular commit where prior to the change Zed works and after it Zed does not (via a git bisect) we might be able to identify what changed, but in the absence of that, this is a cryptomator bug (a filesystem should never crash) and I recommend you file an issue with them.
Good luck!
Check for existing issues
Describe the bug / provide steps to reproduce it
I work with my projects using an encrypted Cryptomator drive via fuse-t (рerhaps it matters, python projects with the pytrightconfig configuration). Earlier, until about version 0.149-150, everything was fine, files were opened, edited, but with the latest updates, when opening the project folder and trying to open the file, the cryptomator disk (fuse-t) crashes, I have to forcibly lock the disk.
After reopening, next to the file that was previously attempted to open, appears the macos service file "._" (with the name of the target file). I installed an earlier version of Zed for verification and the problem was gone.
Environment
Zed: v0.154.2 (Zed) OS: macOS 13.6.9 Memory: 16 GiB Architecture: aarch64
If applicable, add mockups / screenshots to help explain present your vision of the feature
No response
If applicable, attach your Zed.log file to this issue.
Zed.log