-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to Login to Bitwarden #65
Comments
Looks like the app got assigned 256mb, which is probably not enough to handle the 512mb argon2 configuration. |
Does it fail before asking you for a 2FA (if you have one)? |
yes, it fails before 2FA (have Yukikey or Authy options) |
Then this is definitely caused by the KDF settings. Unfortunately I have no control over how much memory system lets the Keyguard use, so there's no solution from my side. |
I tried changing the KDF memory to 256 - same error. |
It should be less then 256mb, as the app also needs some memory to draw itself etc. |
Okay, I changed it to 128mb and it worked - thanks. |
App should now show a proper error message if OOM happens during KDF usage 51dd09a |
I installed the app on an S23U & Pixel 8 Pro. Got the following error when logging into Bitwarden:
"Failed to allocate a 1040 byte allocation with 133680 free bytes and 130KB until OOM, target footprint 268435456, growth limit 26843545; giving up on allocation because <1% of heap free after GC."
Wonder if it has anything to do with my KDF settings (Memory 512 MB, Iterations 10, parallelism 8)
The text was updated successfully, but these errors were encountered: