I am running the latest version of Cryptomator (1.4.0) and Dropbox (63.4.107) on Win 10 Pro (1803 w/ all avail updates).
In trying to copy a 396KB PDF file from my laptop to my vault, I get a “not enough memory” error message. This happens whether the vault is mounted as a Dokany or WebDAV resource. Exact error message is:
This is on top of an annoying issue where some files in my vault cannot be removed from the same system that created the file. I have to remove them from another system (PC or mobile device).
I never had these problems when I first started using Cryptomator. I wish I could remember what version that was. But, it seems like since this 1.4.0 release (and maybe the one prior), I have been having more and more problems.
Any help that can be provided would be appreciated. Otherwise, I may just give up on Cryptomator all together. If I do, would it be possible to get my app purchases (Android and iOS) refunded?
Seems that there’s an issue with pdf files and network drives for specific windows Setups.
I can not reproduce it as my PDFs do not throw that exeption.
Here’s a related post from the adobe forum. https://forums.adobe.com/thread/635836
For me, though, the file had already been in my Cryptomator vault for some time. I only ran into this problem while I was trying to put all of the files in my vault into a new encrypted ZIP file located on my local SSD using the latest version of 7zip. It’s part of my monthly backup practice. 7zip complained it could not access that PDF file along with a couple other files.
I noticed the file property for the PDF file in question was flagged “read-only”. So, I copied the PDF to my local system, unchecked “read-only”, and tried to copy it back into my mounted vault. That’s when I ran into this “not enough memory” error.
Between this problem and the other one I’ve been having where it sometimes won’t let me delete files from Windows, I’m starting to lose confidence in Cryptomator as my multiplatform encrypted storage solution. I may have to give up and pay for Boxcryptor.
I think I had seen reference to that in another post that I came across. It would be nice if that addressed the issues I’m having. I wonder how soon we’ll see the problem discussed in that posting fixed?
WARNING: Removing the alternate streams may cause issues with copies of the files stored on these cloud providers. I was not concerned and deleted the alternate streams, but YMMV. You have been warned.