You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I unlock the Vault, Goldwarden wants several Gigabytes of RAM. While this generally isn't an immediate issue for a modern 16GB+ machine, it's can cause excessive loading times or even OOM killings on older 8GB, let alone 4GB, machines.
I have about 500 entries in my vault, but I can still reproduce the problem after logging out, so this really seems like a bug.
On a 4GB machine with nothing else running, unlock takes like 10 seconds:
First small bump is opening goldwarden, huge peak is unlocking, the drop is what happens after unlocking is complete. When lower on free RAM (under 2 GB) it can take upwards of 30 seconds due to excessive swapping.
edit: this repeats when locking and unlocking again without restarting. Tested with a vault that has just one entry.
Fedora 41
Goldwarden 0.3.6
The text was updated successfully, but these errors were encountered:
itsTyrion
changed the title
Excessive memory usage during unlock with flatpak version
Excessive memory usage during unlock
Dec 2, 2024
When I unlock the Vault, Goldwarden wants several Gigabytes of RAM. While this generally isn't an immediate issue for a modern 16GB+ machine, it's can cause excessive loading times or even OOM killings on older 8GB, let alone 4GB, machines.
I have about 500 entries in my vault, but I can still reproduce the problem after logging out, so this really seems like a bug.
On a 4GB machine with nothing else running, unlock takes like 10 seconds:
First small bump is opening goldwarden, huge peak is unlocking, the drop is what happens after unlocking is complete. When lower on free RAM (under 2 GB) it can take upwards of 30 seconds due to excessive swapping.
edit: this repeats when locking and unlocking again without restarting. Tested with a vault that has just one entry.
Fedora 41
Goldwarden 0.3.6
The text was updated successfully, but these errors were encountered: