Well, I would open my task manager an kill every program/process (except Cryptomator and of course system) that does consume resources or is not really needed. Step by step and always have a look at the Cryptomator usage.
When it suddenly drops, you likely have your app detected.
Most often these are (like @infeo already mentioned): malware protection, anti virus, indexing apps, backup processes, sync processes.
Please don’t get me wrong: I’m not saying that you doesn’t need malware protection or antivirus. But there are good ones and there are bad ones. So besides it’s function you can identify the app by excluding them.
Thank you infeo, I installed “handle” and found out that indeed one of my Cloud Sync applications (for pCloud) is actually accessing the (encrypted) vault.
It is another matter, why pCloud is doing that for so long. I’ll clarify with pcloud.
But what you might be able to help with: why is that a problem for Cryptomator? Afterall. Pcloud is uploading only (in my setup). I never change the files in the Vault anywhere else.
So why is that such a challenge for Cryptomator? The files do not change!
Also: I just discovered: even if I stop pCloud sync (exit the app, nothing shown in Task Manager), Cryptomator carries on computing (60% of CPU). Now nothing (!) accesses the Vault (as reported by Handle). Still 60%.
I am apparently unable to generate interest. But this situation is just carries on 45-60% CPU usage by Cryptomator, even though no matching handles on the Vault, no access to it by anything I can establish. At any rate, there are no changes to the Vault either, so there is nothing to process.
I really would like to help, but I cannot reproduce this. I have cryptomator installed on 3 machines now, from high performance PC to an outdated notebook. No matter if I use dokany or webdav, mounted drives or not, sync active or not. If I do not touch the files inside a vault cryptomator app does not use the CPU (see above).
So I’m afraid I’m out of support here. Maybe someone else has an Idea.
Hi, the new version helped or my reorg of the what is being synced to cloud services.
I took the opportunity provided by the need to essentially re-create the vault to accommodate the new vaul-format and reorganized my storage. Now Cryptomator is the only background process that writes into the folder where my Vault resides. I tested it as described by infeo: no other process has a handle on the path.
The CPU usage of Cryptomator is ow 12-13% (again, mighty PC).
Is that now OK and needs to be accepted?
I can probably tolerate that, but given that I frequently do not do changes to the Vault the whole day, it still seems to be high and I’d like to know what is being computed that feverishly.
About 95% of the time I hibernate and wake the workstation. Booting takes a long time (even though from an SSD drive), as I have a large number of disks and a zillion apps installed, together with a large number of services that run in the background. So I hibernate.
It would be worth evaluating if after a shutdown Cryptomator causes a high CPU usage. And if this is the case, a workaround may be writing a small script that restarts the Cryptomator process after hibernation.
Thanks, that’s what I’ll have to do, I guess. The problem ist, I have zero skills to do but but I’ll have to research.
I can confirm now that that is indeed the pattern: When my PC returns from hibernation, Cryptomator goes to 12-13% CPU usage. If I close and restart the client, it goes down to almost 0%, if there is nothing to do (=most of the time).
I go into hibernation again, and when I come back (PC wakes) CM will come up to 12-13% CPU use.
So to fix this by a script, it would have to
start automatically upon return from hibernation (only)
kill the Cryptomator process
reopen the vault(s) (which is a problem is I don’t want to store the passphrase)
Does anyone have the skills to hammer together a script like that?
I too have CPU usage issues. However I don’t even hibernate or put to sleep my laptop.
My 8th gen i7 proc is normally used by your app 0%, but after some time (few hours ?) it goes to 18% and stays at this level.
The app is fully responsive. I didn’t even open the vault (but I have one on my list) - just turned on the app. Any logs, debug info I could share so you could investigate ?