https://bugs.kde.org/show_bug.cgi?id=467083
Riccardo Robecchi <sephiroth...@hotmail.it> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |REPORTED
--- Comment #2 from Riccardo Robecchi <sephiroth...@hotmail.it> ---
(In reply to Nate Graham from comment #1)
> What encryption backend is your vault using?
>
> What process exactly uses up all the memory when you unlock the vault?
I'm using cryfs. I've just tested this, and it's the cryfs process taking up
all the memory. It seems like this is intentional:
https://github.com/cryfs/cryfs/issues/335#issuecomment-652338744
Cryfs is currently the default (it's the first on the list) when creating a new
vault. It would be good to inform the user of this limitation, as it seems like
it is intentionally made to use 4 GB of RAM: this makes it impossible to use it
on devices with 4 GB of RAM or less.
>From my limited testing, gocryptfs appears to use a lot less memory while
providing similar (if not even better) performance.
--
You are receiving this mail because:
You are watching all bug changes.
