I have an application that I am running on an HTC EVO and an HTC
Incredible. At one point it loads in 10+ new bitmaps. The Evo runs
fine, the Incredible runs out of memory. I have been using 'dumpsys
meminfo' to debug the problem. I noticed something odd right away.
These are numbers on initial boot..
EVO
** MEMINFO in pid 2677 [my.app.here] **
native dalvik other total limit
bitmap nativeBmp
size: 19348 5767 N/A 25115 24576
N/A N/A
allocated: 17110 4794 N/A 21904 N/A
8445 0
Incredible
** MEMINFO in pid 3474 [my.app.here] **
native dalvik other total limit
bitmap nativeBmp
size: 19356 5447 N/A 24803 24576
N/A N/A
allocated: 16589 4018 N/A 20607 N/A
11323 0
The Bitmap field is much higher on the Incredible than on the EVO. As
I load more bitmaps this differences grows and grow until I run out of
memory with...
E/dalvikvm-heap( 3474): 515520-byte external allocation too large for
this process.
E/dalvikvm( 3474): Out of memory: Heap Size=5767KB, Allocated=3154KB,
Bitmap Size=18681KB
E/ ( 3474): VM won't let us allocate 515520 bytes
Why is it that the bitmap sizes are larger on the Incredible? Is
there something in the OS I can look at this will explain this?
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
