netcharm / keepassdroid

Automatically exported from code.google.com/p/keepassdroid
0 stars 1 forks source link

Run out of memory #188

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.Starting the app on Motorola Defy will get the message above
2.App does not open, data not visible
3.

What is the expected output? What do you see instead? the starting screen

What version of the product are you using? On what operating system?
keepass 1.0 on android 2.1

Please provide any additional information below.
Tried to delete something in the memory but didnt help

Original issue reported on code.google.com by Reiner.H...@googlemail.com on 10 Jun 2011 at 7:10

GoogleCodeExporter commented 8 years ago
How large is your keepass file?

Original comment by bpel...@gmail.com on 25 Jun 2011 at 4:50

GoogleCodeExporter commented 8 years ago
Hi!

I think I have the same issue on my Galaxy S, though I can start the 
application. It's just when I try to open my KeePass database, I get an error 
message: "The phone run out of memory while parsing the database. It may be too 
large for your phone."

I'm running KeePassDroid ver 1.9.5 on Android 2.3.3. The size of my kbdx-file 
is about 6.6 Mb.

The same in older kbd-format is 4.3 Mb and runs fine with KeePassDroid.

Hope you can get this fixed.

Regards,
Rauno

Original comment by Rauno.Uu...@gmail.com on 24 Oct 2011 at 12:20

GoogleCodeExporter commented 8 years ago
I was about to report the following, but I am no longer receiving this error 
(ie it opens fine and works well for me):

I'm getting the same error. My kbdx file is 2.56 MiB (and I use a 187 byte key 
file). The app had been working quite well for some time (I sync with dropbox), 
but recently gave me the out-of-memory error.

android 2.3.7, 436 MB total memory, KeePassDroid 1.9.8

Original comment by pckuj...@gmail.com on 2 Mar 2012 at 8:24

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
Open .kdbx file on DroidX.  Has not worked for last two KeePass updates on 
DroidX. File works fine on iPad (iOS6), Macs and Win7 PC when creating on 
iPad2, Mac or Win7 PC. (I don't try to create the actual file on DroidX since 
it only reads KeePass v2.0 .kdbx files and is easier to work on Mac or PC. Test 
file of very small size created on DroidX as a .kdb file does work fine.

What is the expected output? What do you see instead? 
Open .kdbx file and enter password then display data. Instead see error, "The 
phone ran out of memory while parsing your database. It may be too large for 
your phone."

What version of the product are you using? On what operating system?
keepass v1.9.18.3 on android v2.3.4 on DroidX Verizon 4.5.621 (all platforms 
using most current update as of 20120926)

Please provide any additional information below.
My kdbx files are typically 21Mb - 25Mb now. Why so big? Just minimal data and 
standard icons? 
DroidX has 8 Gb internal RAM and 32 Gb SD card.  Does not open these .kdbx 
files from internal or SD locations.
Systems have been rebooted from shutdown (and removal of battery on DroidX).  
All other apps work fine.
Does not work with or without a key file. 

Original comment by maple.g...@gmail.com on 27 Sep 2012 at 1:39

GoogleCodeExporter commented 8 years ago
bump

Original comment by michelka...@gmail.com on 29 Dec 2012 at 10:00

GoogleCodeExporter commented 8 years ago
I use 1.99.2...db file kdbx is about 18mb. I have a Droid Bionic. Get out of 
mem error. Colluege gets no error with same file on google nexus.

Original comment by thumper3...@gmail.com on 21 Feb 2013 at 8:03

GoogleCodeExporter commented 8 years ago
Regarding entry #4 (six months later and same problem):
Still get out of memory while parsing file. File size is 19.2 Mb. KeePassDroid 
v1.99.2 (current).  KeePass works fine on all my other platforms.  No other app 
on Droid creates this error.  Droid X1 with latest Verizon s/w and 8 Gb 
internal plus 32 Gb flash mem. Why is 19.2 Mb a problem?

Original comment by maple.g...@gmail.com on 21 Feb 2013 at 9:54