PhilippC
Arg_OutOfMemoryException :: Is there a max limit on keepass db size Keepass2Android can handle?
What version of Keepass2Android are you using? 1.12-r5
The keepass database I'm opening is stored locally however it is synced by a file sync service.
When starting Keepass2Android it is configured to automatically load the last chosen database. It does so. However, it seems to open a cached version of the database (content://), as when the database file has been updated on the file system by the sync servicein the meantime, Keepass2Android does detect this and prints a related message, but the opened database still has the old content.
When forcing Keepass2Android to load the newest file by clicking "synchronize", the process fails with an Arg_OutOfMemoryException error message shown.
When I closed the database and try to open the latest version form the filesystem, again a Arg_OutOfMemoryException error message shown and the loading fails.
The keepass file actually is quite large, around 100 MB, however there is more than sufficient memory on the device, so it should never hit a system limit.
The last change on the system was a OS update (Samsung One-UI 6.1, Android 14 with Jun 2025 security patches).
As this has worked in the past, I'm wondering what the cause could be. Is there a memory limit within keepass2android? Or does the error indicate Keepass2Android is not given sufficient memory by the OS? Anything i can change to solve this?
Having read the guide on the file handling in Keepss2Android, I guess the execption is thrown while the app tries to copy the database file from the Android filesystem via content:// to its app context.
Which would mean this is the code where we run into the exception:
I tend to convert this issue to a bug. However, it would be helpful if the dev tea could have a look at my questions above to learn if this is intended behaviour or not.
Moved away from Keepass2Android because of this error and because I wasn't able to find a fix and get support.