On Oct 30, 12:23 pm, Sekar shake...@yahoo.com wrote:
10-30 14:59:50.841: INFO/dalvikvm-heap(23490): Forcing collection of
SoftReferences for 134217760-byte allocation
Curiously, 134217760 is 0x0820. Something went wrong in here.
The original poster's allocation was 0x0A24, also
When an orientation occurs, your activity is being destroyed, and a
new instance is created. The problem is that some references are still
kept in memory.
Some useful resources to read: Avoiding memory leaks (http://android-
developers.blogspot.com/2009/01/avoiding-memory-leaks.html) and
Faster
I have a MapView App that I wrote a while back in 1.1. It worked after
I migrated it to 1.5. It is throwing the same exception you are seeing
in 1.6. The App stopped working after the 1.6 system update. I got a
chance today to upgrade my eclipse plugin to 0.9.5 and get the 1.6 sdk
and deploy the
Here my logcat:
E/dalvikvm-heap( 961): Out of memory on a 167772196-byte allocation.
I/dalvikvm( 961): main prio=5 tid=3 RUNNABLE
I/dalvikvm( 961): | group=main sCount=0 dsCount=0 s=N
obj=0x4001ab08 self=0xbc60
I/dalvikvm( 961): | sysTid=961 nice=0 sched=0/0 handle=-1343996920
From the stack trace it seems that your trying to allocate 160 MB of
memory. And for one app the max heap size in Android is 16 Mb (if i
remember correctly). That's why the outofmemoryerror. Don't know why
are you allocating that much memory though??
-Mika
On Oct 1, 3:43 pm, Stefan
Hi,
On Oct 1, 4:07 pm, Mika mika.ristim...@tkk.fi wrote:
From the stack trace it seems that your trying to allocate 160 MB of
memory. And for one app the max heap size in Android is 16 Mb (if i
remember correctly). That's why the outofmemoryerror. Don't know why
are you allocating that much
From the stack trace it looks like the memory allocation is done
inside the Map.resize function.
So you most likely set a enormous size after the orientation change to
your mapview.
Adding some Log.i functions might narrow it down to the source of the
problem.
On 1 Okt., 16:18, Stefan
Actually I thought you set the size by your self, didn't notice that
you posted the xml file.
So you could have wrote the size to logcat with Log. So in this I
don't know whats causing the view to consume memory that way it does.
On 1 Okt., 17:25, Stefan ebay-dah...@web.de wrote:
Hi
On Oct 1,
hi,
i have test it without the mapView and my app work fine after i rotate
the emulator. so the problem is the mapView.
Can the display size a problem?? Because the button, which is over the
MapView (if it will be activated), is positionated at the button of
the display.
But than i think, the
9 matches
Mail list logo
