bitwarden AppImage crashes, cant get in to my vault. HELP!

Version 2025.1.1
SDK ‘main (28c7e29)’
Shell 33.2.1
Renderer 130.0.6723.137
Node 20.18.1
Architecture x64

I have been using bitwarden without an issue on fedora with AppImages for quite a while but since last update just after pressing enter after my password it crashes without any warning and closes. I did increased my encryption key settings but years ago I use: Argon2id, KDF iterations 6, KDF memory 1024, KDF parallelism 4. My guess is last update did something that limits maybe memory or something? As I could not find anything about this on the internet is not a common issue. I did erase the .config/Bitwarden folder to see if there was a corruption or something there but the crash persists.

last part of app.log (the last thing i did was try to log and it crashed so it should be here at the end)
[2025-01-22 16:34:34.896] [info] Migrator PasswordOptionsMigrator (to version 63) should migrate: false - up
[2025-01-22 16:34:34.897] [info] Migrator GeneratorHistoryMigrator (to version 64) should migrate: false - up
[2025-01-22 16:34:34.897] [info] Migrator ForwarderOptionsMigrator (to version 65) should migrate: false - up
[2025-01-22 16:34:34.897] [info] Migrator MoveFinalDesktopSettingsMigrator (to version 66) should migrate: false - up
[2025-01-22 16:34:34.897] [info] Migrator RemoveUnassignedItemsBannerDismissed (to version 67) should migrate: false - up
[2025-01-22 16:34:34.897] [info] Migrator MoveLastSyncDate (to version 68) should migrate: false - up
[2025-01-22 16:34:35.238] [info] Coredumps are disabled in renderer process
[2025-01-22 16:34:37.735] [info] State version: 68
[2025-01-22 16:34:37.829] [info] Retrieving application id
[2025-01-22 16:34:40.381] [info] Checking for update
[2025-01-22 16:34:41.615] [info] Update for version 2025.1.1 is not available (latest version: 2025.1.1, downgrade is disallowed).
[2025-01-22 16:34:46.130] [info] Retrieving application id

@swayze Welcome to the forum!

It seems, you already deleted the local storage, and since that didn’t change anything, it sounds like a bug to me at first sight (so maybe a bug report on GitHub might be also reasonable → https://github.com/bitwarden/clients/issues → “New issue”).

I’m not that familiar with the Linux packages, but you might download a desktop version prior to 2025.1.1 as a temporary solution.

Otherwise, if you want to access your data, you can also try different desktop app variants for Linux, or use one of the browser extensions or even the web vault (vault.bitwarden.com or vault.bitwarden.eu).

If you reduce your memory to f.e 128, does unlock work again?

I just tried with a new account without changing key settings and I was able to login so it has to do with something related to memory or something that is now limited.
then i tried changing to argon and this different options:

KDF iterations 6, KDF memory 64, KDF parallelism 4/
KDF iterations 6, KDF memory 512, KDF parallelism 4/
KDF iterations 6, KDF memory 768, KDF parallelism 4/
KDF iterations 6, KDF memory 896, KDF parallelism 4/
KDF iterations 6, KDF memory 999, KDF parallelism 4/
KDF iterations 6, KDF memory 1000, KDF parallelism 4/
KDF iterations 6, KDF memory 1012, KDF parallelism 4/
KDF iterations 6, KDF memory 1018, KDF parallelism 4/
KDF iterations 6, KDF memory 1021, KDF parallelism 4/
KDF iterations 6, KDF memory 1023, KDF parallelism 4/
KDF iterations 6, KDF memory 1024, KDF parallelism 4X

just the one with 1024 memory did not let me get in being 1024 the limit of KDF memory allowed to use but the AppImage does not allowed the 1024 but it does 1023 of memory.

I may just decrease my account KDF memory to 1023 and should be fine but this bug should not exist I created a github bug as stated above.