[android-developers] Re: java.lang.OutOfMemoryError after orientation changed

2009-11-03 Thread Mihai Fonoage
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 screen orientation change" (http://android-
developers.blogspot.com/2009/02/faster-screen-orientation-
change.html).

I had similar issues when loading bitmaps, and screen orientation
changes would through an out of memory error almost every time at some
point. The above links helped in solving the issue.

Mihai Fonoage

On Nov 3, 4:45 pm, fadden  wrote:
> On Oct 30, 12:23 pm, Sekar  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 suspiciously
> round.
>
> Is this easily repeatable?  If so, can you file a bug on b.android.com
> and attach the APK to the bug report?

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


[android-developers] Re: java.lang.OutOfMemoryError after orientation changed

2009-11-03 Thread fadden
On Oct 30, 12:23 pm, Sekar  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 suspiciously
round.

Is this easily repeatable?  If so, can you file a bug on b.android.com
and attach the APK to the bug report?

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


[android-developers] Re: java.lang.OutOfMemoryError after orientation changed

2009-11-02 Thread Sekar
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 App again and saw the same error on logcat. I have
another MapView App that was also written a while back. It works
without any issue on 1.6. The main difference between the 2 Apps are
the views in the ViewGroup. In the App that works fine, there is only
1 view (MapView) on the ViewGroup. In the App that now throws the
OutOfmemory Exception, there are several Layouts with several views on
them (including a Mapview) that are assembled together to form the
ViewGroup.


10-30 14:59:50.841: INFO/dalvikvm-heap(23490): Forcing collection of
SoftReferences for 134217760-byte allocation
10-30 14:59:50.911: DEBUG/NetworkLocationProvider(75):
updateWifIScanResults(): 9 APs
10-30 14:59:50.991: DEBUG/dalvikvm(23490): GC freed 3582 objects /
263656 bytes in 146ms
10-30 14:59:50.991: ERROR/dalvikvm-heap(23490): Out of memory on a
134217760-byte allocation.
10-30 14:59:50.991: INFO/dalvikvm(23490): "main" prio=5 tid=3 RUNNABLE
10-30 14:59:50.991: INFO/dalvikvm(23490):   | group="main" sCount=0
dsCount=0 s=N obj=0x4001db08 self=0xbc48
10-30 14:59:50.991: INFO/dalvikvm(23490):   | sysTid=23490 nice=0
sched=0/0 handle=-1343996920
10-30 14:59:50.991: INFO/dalvikvm(23490):   at
com.google.googlenav.map.Map.resize((null):~-1)
10-30 14:59:50.991: INFO/dalvikvm(23490):   at
com.google.android.maps.MapView.onMeasure(MapView.java:536)
10-30 14:59:51.021: INFO/dalvikvm(23490):   at
android.view.View.measure(View.java:7703)
10-30 14:59:51.051: INFO/dalvikvm(23490):   at
android.widget.RelativeLayout.measureChildHorizontal
(RelativeLayout.java:569)
10-30 14:59:51.051: INFO/dalvikvm(23490):   at
android.widget.RelativeLayout.onMeasure(RelativeLayout.java:361)
10-30 14:59:51.051: INFO/dalvikvm(23490):   at
android.view.View.measure(View.java:7703)
10-30 14:59:51.051: INFO/dalvikvm(23490):   at
android.widget.RelativeLayout.measureChildHorizontal
(RelativeLayout.java:569)
10-30 14:59:51.051: INFO/dalvikvm(23490):   at
android.widget.RelativeLayout.onMeasure(RelativeLayout.java:361)
10-30 14:59:51.051: INFO/dalvikvm(23490):   at
android.view.View.measure(View.java:7703)


On Oct 1, 3:07 pm, Stefan  wrote:
> 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 MapView will be rendered, but is not visible for
> the user, because the display size in landscape is to small???
> Is the only way to write a new layout xml file for landscape mode?
>
> Thanks,
> Stefan

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


[android-developers] Re: java.lang.OutOfMemoryError after orientation changed

2009-10-01 Thread Stefan

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 MapView will be rendered, but is not visible for
the user, because the display size in landscape is to small???
Is the only way to write a new layout xml file for landscape mode?

Thanks,
Stefan
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---



[android-developers] Re: java.lang.OutOfMemoryError after orientation changed

2009-10-01 Thread Beowolve

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  wrote:
> Hi
>
> On Oct 1, 5:09 pm, Beowolve  wrote:
>
> > 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.
>
> hmmm, i never set any size in my source code.
>
> > Adding some Log.i functions might narrow it down to the source of the
> > problem.
>
> can you please show me an example. What tag i must set in the Log.i
> function??
> Log.i(TAG,MSG)
>
> I try to use the onConfigurationChanged() functtion. If i set another
> xml file with less content/widgets (only 1 TextView, 1 EditText and 1
> button) it works:
>
> if(config.orientation==Configuration.ORIENTATION_LANDSCAPE)
> {
>                 setContentView(R.layout.ANOTHER_XML_FILE);
>
> }
>
> But i've read, that the onConfigurationChanged - method isn't the best
> choice.
> So if there is a solution without that, i will prefer that.
>
> Thanks,
> Stefan
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---



[android-developers] Re: java.lang.OutOfMemoryError after orientation changed

2009-10-01 Thread Stefan

Hi

On Oct 1, 5:09 pm, Beowolve  wrote:
> 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.

hmmm, i never set any size in my source code.

> Adding some Log.i functions might narrow it down to the source of the
> problem.
>
can you please show me an example. What tag i must set in the Log.i
function??
Log.i(TAG,MSG)


I try to use the onConfigurationChanged() functtion. If i set another
xml file with less content/widgets (only 1 TextView, 1 EditText and 1
button) it works:

if(config.orientation==Configuration.ORIENTATION_LANDSCAPE)
{
setContentView(R.layout.ANOTHER_XML_FILE);
}

But i've read, that the onConfigurationChanged - method isn't the best
choice.
So if there is a solution without that, i will prefer that.

Thanks,
Stefan

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---



[android-developers] Re: java.lang.OutOfMemoryError after orientation changed

2009-10-01 Thread Beowolve

>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  wrote:
> Hi,
>
> On Oct 1, 4:07 pm, Mika  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 memory though??
>
> i don't know it, too. Perhaps it helped, if i show you my xml file:
>
> 
>          xmlns:android="http://schemas.android.com/apk/res/android";
>         android:layout_width="fill_parent"
>         android:layout_height="wrap_content">
>                          android:id="@+id/ak"
>                 android:text="Streckenlänge: 0 km"
>                 android:layout_width="wrap_content"
>                 android:layout_height="wrap_content"
>                 android:paddingTop="15px"
>                 android:layout_marginLeft="5px"
>                 />
>                          android:id="@+id/view1"
>                 android:layout_width="fill_parent"
>                 android:layout_height="2dip"
>                 android:background="#FF00FF00"
>                 android:layout_below="@id/ak"
>                 android:layout_marginTop="5px"/>
>
>                          android:id="@+id/ab"
>                 android:text="Abbiegepunkt hinzufügen:"
>                 android:layout_width="wrap_content"
>                 android:layout_height="wrap_content"
>                 android:layout_below="@id/view1"
>                 android:layout_marginLeft="5px"
>                 android:layout_marginTop="10px"
>                 />
>                          android:id="@+id/left"
>                 android:layout_width="wrap_content"
>                 android:layout_height="wrap_content"
>                 android:background="@drawable/left"
>                 android:layout_below="@id/ab"
>                 android:layout_alignLeft="@id/ab"
>                 android:layout_marginLeft="5px"
>                 android:layout_marginTop="5px"/>
>
>                          android:id="@+id/right"
>                 android:layout_width="wrap_content"
>                 android:layout_height="wrap_content"
>                 android:layout_marginLeft="5px"
>                 android:layout_toRightOf="@id/left"
>                 android:layout_alignTop="@id/left"
>                 android:background="@drawable/right"
>                 />
>
>                          android:id="@+id/view2"
>                 android:layout_width="fill_parent"
>                 android:layout_height="2dip"
>                 android:background="#FF00FF00"
>                 android:layout_below="@id/left"
>                 android:layout_marginTop="5px"/>
>                          android:id="@+id/gefahr"
>                 android:layout_width="wrap_content"
>                 android:layout_height="wrap_content"
>                 android:layout_below="@id/view2"
>                 android:text="Gefahrenpunkt:"
>                 android:layout_marginLeft="5px"
>                 android:layout_marginTop="10px"/>
>                          android:id="@+id/gefahrbild"
>                 android:layout_width="wrap_content"
>                 android:layout_height="wrap_content"
>                 android:text="mit Bild speichern"
>                 android:layout_below="@id/gefahr"
>                 android:layout_marginLeft="5px"
>                 android:layout_marginTop="5px"
>                 />
>                          android:id="@+id/gefahrtext"
>                 android:layout_width="wrap_content"
>                 android:layout_height="wrap_content"
>                 android:text="mit Text speichern"
>                 android:layout_toRightOf="@id/gefahrbild"
>                 android:layout_alignTop="@id/gefahrbild"
>                 android:layout_marginLeft="5px"
>                 />
>                          android:id="@+id/view3"
>                 android:layout_width="fill_parent"
>                 android:layout_height="2dip"
>                 android:background="#FF00FF00"
>                 android:layout_below="@id/gefahrbild"
>                 android:layout_marginTop="5px"/>
>                          android:id="@+id/end"
>                 android:layout_width="fill_parent"
>                 android:layout_height="wrap_content"
>                 android:text="Erfassung stoppen"
>                 android:layout_below="@id/view3"
>                 android:layout_marginLeft="5px"
>                 android:layout_marginTop="10px"
>                 />
>                          xmlns:android="http://schemas.android.com/apk/res/android";
>                 android:layout_width="wrap_content"
>                 android:layout_heig

[android-developers] Re: java.lang.OutOfMemoryError after orientation changed

2009-10-01 Thread Stefan

Hi,

On Oct 1, 4:07 pm, Mika  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 memory though??

i don't know it, too. Perhaps it helped, if i show you my xml file:


http://schemas.android.com/apk/res/android";
android:layout_width="fill_parent"
android:layout_height="wrap_content">














http://schemas.android.com/apk/res/android";
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_below="@id/end">




The picture on my buttons are very small and so i thought, the MapView
is the problem?? I dont have an Overlay or something like that.
In my app, i have a locationListener, which "collect" gps points...
And in my app i can start an intent, where i can take pictures.

So I don't know, why i allocate 160 MB?!

Thanks,
Stefan


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---



[android-developers] Re: java.lang.OutOfMemoryError after orientation changed

2009-10-01 Thread Mika

>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  wrote:
> 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
> I/dalvikvm(  961):   at com.google.googlenav.map.Map.resize
> ((null):~-1)
> I/dalvikvm(  961):   at com.google.android.maps.MapView.onMeasure
> (MapView.java:536)
> I/dalvikvm(  961):   at android.view.View.measure(View.java:7703)
> I/dalvikvm(  961):   at
> android.widget.RelativeLayout.measureChildHorizontal
> (RelativeLayout.java:569)
> I/dalvikvm(  961):   at android.widget.RelativeLayout.onMeasure
> (RelativeLayout.java:361)
> I/dalvikvm(  961):   at android.view.View.measure(View.java:7703)
> I/dalvikvm(  961):   at android.widget.RelativeLayout.measureChild
> (RelativeLayout.java:554)
> I/dalvikvm(  961):   at android.widget.RelativeLayout.onMeasure
> (RelativeLayout.java:377)
> I/dalvikvm(  961):   at android.view.View.measure(View.java:7703)
> I/dalvikvm(  961):   at android.view.ViewGroup.measureChildWithMargins
> (ViewGroup.java:2989)
> I/dalvikvm(  961):   at android.widget.FrameLayout.onMeasure
> (FrameLayout.java:245)
> I/dalvikvm(  961):   at android.view.View.measure(View.java:7703)
> I/dalvikvm(  961):   at android.widget.LinearLayout.measureVertical
> (LinearLayout.java:464)
> I/dalvikvm(  961):   at android.widget.LinearLayout.onMeasure
> (LinearLayout.java:278)
> I/dalvikvm(  961):   at android.view.View.measure(View.java:7703)
> I/dalvikvm(  961):   at android.view.ViewGroup.measureChildWithMargins
> (ViewGroup.java:2989)
> I/dalvikvm(  961):   at android.widget.FrameLayout.onMeasure
> (FrameLayout.java:245)
> I/dalvikvm(  961):   at android.view.View.measure(View.java:7703)
> I/dalvikvm(  961):   at android.view.ViewRoot.performTraversals
> (ViewRoot.java:747)
> I/dalvikvm(  961):   at android.view.ViewRoot.handleMessage
> (ViewRoot.java:1613)
> I/dalvikvm(  961):   at android.os.Handler.dispatchMessage
> (Handler.java:99)
> I/dalvikvm(  961):   at android.os.Looper.loop(Looper.java:123)
> I/dalvikvm(  961):   at android.app.ActivityThread.main
> (ActivityThread.java:4203)
> I/dalvikvm(  961):   at java.lang.reflect.Method.invokeNative(Native
> Method)
> I/dalvikvm(  961):   at java.lang.reflect.Method.invoke(Method.java:
> 521)
> I/dalvikvm(  961):   at com.android.internal.os.ZygoteInit
> $MethodAndArgsCaller.run(ZygoteInit.java:791)
> I/dalvikvm(  961):   at com.android.internal.os.ZygoteInit.main
> (ZygoteInit.java:549)
> I/dalvikvm(  961):   at dalvik.system.NativeStart.main(Native Method)
> I/dalvikvm(  961):
> D/AndroidRuntime(  961): Shutting down VM
> W/dalvikvm(  961): threadid=3: thread exiting with uncaught exception
> (group=0x4001aa28)
> E/AndroidRuntime(  961): Uncaught handler: thread main exiting due to
> uncaught exception
> E/AndroidRuntime(  961): java.lang.OutOfMemoryError
> E/AndroidRuntime(  961):        at com.google.googlenav.map.Map.resize
> (Unknown Source)
> E/AndroidRuntime(  961):        at
> com.google.android.maps.MapView.onMeasure(MapView.java:536)
> E/AndroidRuntime(  961):        at android.view.View.measure(View.java:
> 7703)
> E/AndroidRuntime(  961):        at
> android.widget.RelativeLayout.measureChildHorizontal
> (RelativeLayout.java:569)
> E/AndroidRuntime(  961):        at
> android.widget.RelativeLayout.onMeasure(RelativeLayout.java:361)
> E/AndroidRuntime(  961):        at android.view.View.measure(View.java:
> 7703)
> E/AndroidRuntime(  961):        at
> android.widget.RelativeLayout.measureChild(RelativeLayout.java:554)
> E/AndroidRuntime(  961):        at
> android.widget.RelativeLayout.onMeasure(RelativeLayout.java:377)
> E/AndroidRuntime(  961):        at android.view.View.measure(View.java:
> 7703)
> E/AndroidRuntime(  961):        at
> android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:2989)
> E/AndroidRuntime(  961):        at android.widget.FrameLayout.onMeasure
> (FrameLayout.java:245)
> E/AndroidRuntime(  961):        at android.view.View.measure(View.java:
> 7703)
> E/AndroidRuntime(  961):        at
> android.widget.LinearLayout.measureVertical(LinearLayout.java:464)
> E/AndroidRuntime(  961):        at
> android.widget.LinearLayout.onMeasure(LinearLayout.java:278)
> E/AndroidRuntime(  961):        at android.view.View.measure(View.java:
> 7703)
> E/AndroidRuntime(  961):        at
> android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:2989)
> E/AndroidRuntime(  961):        at android.widget.FrameLayout.onMeasure
> (FrameLayout.java:245)
> E/AndroidRuntime(  961):        at android.view.View.measure(View.java:
> 7703

[android-developers] Re: java.lang.OutOfMemoryError after orientation changed

2009-10-01 Thread Stefan

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
I/dalvikvm(  961):   at com.google.googlenav.map.Map.resize
((null):~-1)
I/dalvikvm(  961):   at com.google.android.maps.MapView.onMeasure
(MapView.java:536)
I/dalvikvm(  961):   at android.view.View.measure(View.java:7703)
I/dalvikvm(  961):   at
android.widget.RelativeLayout.measureChildHorizontal
(RelativeLayout.java:569)
I/dalvikvm(  961):   at android.widget.RelativeLayout.onMeasure
(RelativeLayout.java:361)
I/dalvikvm(  961):   at android.view.View.measure(View.java:7703)
I/dalvikvm(  961):   at android.widget.RelativeLayout.measureChild
(RelativeLayout.java:554)
I/dalvikvm(  961):   at android.widget.RelativeLayout.onMeasure
(RelativeLayout.java:377)
I/dalvikvm(  961):   at android.view.View.measure(View.java:7703)
I/dalvikvm(  961):   at android.view.ViewGroup.measureChildWithMargins
(ViewGroup.java:2989)
I/dalvikvm(  961):   at android.widget.FrameLayout.onMeasure
(FrameLayout.java:245)
I/dalvikvm(  961):   at android.view.View.measure(View.java:7703)
I/dalvikvm(  961):   at android.widget.LinearLayout.measureVertical
(LinearLayout.java:464)
I/dalvikvm(  961):   at android.widget.LinearLayout.onMeasure
(LinearLayout.java:278)
I/dalvikvm(  961):   at android.view.View.measure(View.java:7703)
I/dalvikvm(  961):   at android.view.ViewGroup.measureChildWithMargins
(ViewGroup.java:2989)
I/dalvikvm(  961):   at android.widget.FrameLayout.onMeasure
(FrameLayout.java:245)
I/dalvikvm(  961):   at android.view.View.measure(View.java:7703)
I/dalvikvm(  961):   at android.view.ViewRoot.performTraversals
(ViewRoot.java:747)
I/dalvikvm(  961):   at android.view.ViewRoot.handleMessage
(ViewRoot.java:1613)
I/dalvikvm(  961):   at android.os.Handler.dispatchMessage
(Handler.java:99)
I/dalvikvm(  961):   at android.os.Looper.loop(Looper.java:123)
I/dalvikvm(  961):   at android.app.ActivityThread.main
(ActivityThread.java:4203)
I/dalvikvm(  961):   at java.lang.reflect.Method.invokeNative(Native
Method)
I/dalvikvm(  961):   at java.lang.reflect.Method.invoke(Method.java:
521)
I/dalvikvm(  961):   at com.android.internal.os.ZygoteInit
$MethodAndArgsCaller.run(ZygoteInit.java:791)
I/dalvikvm(  961):   at com.android.internal.os.ZygoteInit.main
(ZygoteInit.java:549)
I/dalvikvm(  961):   at dalvik.system.NativeStart.main(Native Method)
I/dalvikvm(  961):
D/AndroidRuntime(  961): Shutting down VM
W/dalvikvm(  961): threadid=3: thread exiting with uncaught exception
(group=0x4001aa28)
E/AndroidRuntime(  961): Uncaught handler: thread main exiting due to
uncaught exception
E/AndroidRuntime(  961): java.lang.OutOfMemoryError
E/AndroidRuntime(  961):at com.google.googlenav.map.Map.resize
(Unknown Source)
E/AndroidRuntime(  961):at
com.google.android.maps.MapView.onMeasure(MapView.java:536)
E/AndroidRuntime(  961):at android.view.View.measure(View.java:
7703)
E/AndroidRuntime(  961):at
android.widget.RelativeLayout.measureChildHorizontal
(RelativeLayout.java:569)
E/AndroidRuntime(  961):at
android.widget.RelativeLayout.onMeasure(RelativeLayout.java:361)
E/AndroidRuntime(  961):at android.view.View.measure(View.java:
7703)
E/AndroidRuntime(  961):at
android.widget.RelativeLayout.measureChild(RelativeLayout.java:554)
E/AndroidRuntime(  961):at
android.widget.RelativeLayout.onMeasure(RelativeLayout.java:377)
E/AndroidRuntime(  961):at android.view.View.measure(View.java:
7703)
E/AndroidRuntime(  961):at
android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:2989)
E/AndroidRuntime(  961):at android.widget.FrameLayout.onMeasure
(FrameLayout.java:245)
E/AndroidRuntime(  961):at android.view.View.measure(View.java:
7703)
E/AndroidRuntime(  961):at
android.widget.LinearLayout.measureVertical(LinearLayout.java:464)
E/AndroidRuntime(  961):at
android.widget.LinearLayout.onMeasure(LinearLayout.java:278)
E/AndroidRuntime(  961):at android.view.View.measure(View.java:
7703)
E/AndroidRuntime(  961):at
android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:2989)
E/AndroidRuntime(  961):at android.widget.FrameLayout.onMeasure
(FrameLayout.java:245)
E/AndroidRuntime(  961):at android.view.View.measure(View.java:
7703)
E/AndroidRuntime(  961):at
android.view.ViewRoot.performTraversals(ViewRoot.java:747)
E/AndroidRuntime(  961):at android.view.ViewRoot.handleMessage
(ViewRoot.java:1613)
E/AndroidRuntime(  961):at android.os.Handler.dispatchMessage
(Handler.java:99)
E/AndroidRuntime(  961):at android.os.Looper.loop(Looper.java:
123)
E/AndroidRuntime(  961):at android.app.ActivityThread.main
(ActivityThread.java:4203)
E/AndroidRuntime(  961):at
java.lang.re