The phone ran out of memory while parsing your database

[wolandtel]

I've installed keepassdroid on a new phone (Xiaomi Mi 8) with android 8.0. Trying to open 2,1Mb kdbx database I've got subj. I allowed keepassdroid access to the system memory (btw it didn't request it).

[haloway13]

I have a OnePlus 6. I have reason to believe that I have plenty of memory/space (33GB) on my phone. DB is at 340k (about 300 entries). Opens fine on computer, fails with the message: "The phone ran out of memory while parsing your database. It may be too large for your phone."

Any suggestions for me?

[twt2]

I suddenly started having this problem today. Possibly related: there's a new version of KeePassXC I'm using on my desktop and it seems likely there's an incompatibility between them. I don't know the size of my database but it hasn't changed significantly since a day or two ago. I sync using DropBox and have been "bitten" by a bug that scrambles the database when I edit it using KeePassDroid multiple times within a few minutes. This is NOT the same error as I see when that happens.

EDIT: I decided to create some test files using KeePassXC 2.5.1 and KeePass 2.41 to see if I could replicate the issue in KeePassDroid 2.4.1. Strangely, the problem has disappeared on the original file, so I presume it was a transitory issue, maybe due to a subtle sync issue with DropBox. ?? (When DropBox scrambles the file, it's usually damaged everywhere and can no longer be opened, not just on KeePassDroid.)

EDIT2: I'm getting the error again today. (26 November 2019) All of my test databases open without the memory error (though they only have a one or a few data entries each). I may try rebooting the phone, but this is quite disappointing.

EDIT3: a reboot didn't help. The database won't open in KeePassDroid but it opens fine in KeePassXC AND KeePass2 in Ubuntu. (At first I thought it was failing to open in KeePass2 but I was apparently opening the wrong file.)

EDIT4: Saving a "fresh" copy of the database from either KeePassXC or KeePass2 makes it open-able from KeePassDroid. The difficult database is 225.5kB and the re-saved databases are 225.4kB (KeePassXC) and 224.9kB (KeePass2). According to KeePass2 I have 748 entries in 12 folders (categories) plus 6 entries in the recycle bin.

EDIT5: The keepass2android app was able to open the problematic file.

[twt2]

Just leaving a reply message in case the thread isn't getting updated with all my edits.

If anyone can suggest a different sort of test file I could produce that would help resolve this (or at least give me a useful workaround when I can't get the database to open on my phone but I don't have access to a Linux computer).

NOTE: KeePass2 is an ugly mono program in linux but it gives useful information not easily visible from other KeePass compatible applications.

[J-Jamet]

I'm working on this issue in my fork and I notified several structural problems:

• The parser is an XML pull and the nextText() method that retrieves data from the XML may not work properly if there is a large amount of data to retrieve. (No real solution, maybe use a parser SAX but less fast and forced to redo all the parser.)
• The data is only exchanged with byte arrays, which uses a large amount of information for the transfer. (Better to use stream with buffer and store temp files in app storage)
• Zip files are only done on the fly by converting byte array. (Which can not be done with large volumes, solution is to use stream)
• Binary data is not stored in the same way for KDBX3.1 or KDBX4.0 files, which can cause bugs.(https://github.com/keepassxreboot/keepassxc-specs/blob/master/kdbx-xml/rfc.md)
• The Argon2 key derivation with a large RAM set in KeePass XC prevents proper opening. (solution is to lower the memory used and increase the iterations)