OutOfMemoryError: bitmap size exceeds VM budget #112
Comments
|
From thilo.mu...@gmail.com on March 29, 2011 05:43:07 I didn't try to execute your code, but by looking at it i can already see that you are not using the overlay classes as intended. As each overlay consumes > 3 MB of RAM, having more than 3-4 overlays will eat up the available heap space completely (see: https://code.google.com/p/mapsforge/wiki/OverlayAPI ). In version 0.2.2 the overlay classes have therefore been refactored to display more than one polygon on a single overlay. You have to upgrade to the 0.2.2 version of the map library. As you can see in the latest version of the OverlayMapViewer sample activity ( https://code.google.com/p/mapsforge/source/browse/trunk/Applications/Android/Samples/src/org/mapsforge/applications/android/samples/OverlayMapViewer.java ), all polygons should be added into one ArrayWayOverlay. Only this single ArrayWayOverlay must then be added to the overlay list from the MapView. Please let me know if the discussed changes solve the problem. |
|
From hansgeor...@gmail.com on March 29, 2011 08:46:36 Ok, i switched back to 0.2.2 (line code #79 and moved line code 270 & 271 after 259. also moved line code 274 after 277. 03-29 17:24:27.984: DEBUG/dalvikvm(28247): GC_CONCURRENT freed 1052K, 45% free 5556K/9927K, external 6369K/7890K, paused 2ms+4ms |
|
From hansgeor...@gmail.com on March 29, 2011 08:46:36 ...time(28247): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597) |
|
From hansgeor...@gmail.com on March 29, 2011 09:05:56 when I switch back to map version 0.2.1 and use the latest code there is no null pointer problem. |
|
From thilo.mu...@gmail.com on April 04, 2011 10:08:35 I am not able to reproduce the NullPointerException. Can you give a detailed description how to trigger it? The other error messages should be fixed if you use the latest germany file from our public FTP server ( ftp://ftp.mapsforge.org/europe/germany-0.2.2.map ). |
|
From tdh...@gmail.com on April 30, 2011 11:31:18 I also have this problem. It comes when I exit my app, and then run it again. I only have 2 layers. 04-30 19:26:22.974: ERROR/dalvikvm-heap(8505): 131072-byte external allocation too large for this process. Maybe a memory leak or something? |
|
From tdh...@gmail.com on April 30, 2011 13:18:28 Aha, I found where my problem was: Each time I ran the app it was creating a new activity (and hence using more memory) rather than just going back to the already-existing activity. Fixed by adding android:launchMode="singleTask" to the manifest. You guys should probably do the same for AdvancedMapViewer -- otherwise you get a stack of map activities and can 'back' through them, and there're other bad effects. |
|
From thilo.mu...@gmail.com on May 01, 2011 11:33:13 Please do not confuse different issues here. An OutOfMemoryError may have many causes, one of them are memory leaks. The map rendering uses several MB of RAM for read buffers and bitmap caches, each overlay consumes at least another 3 MB (see https://code.google.com/p/mapsforge/wiki/OverlayAPI#Performance_and_limitations ). The maximum available RAM (heap size) depends on the device configuration. In worst case it is only 16 MB, but many newer devices have a larger value (typically 24-48 MB). Unfortunately there is now way to change the heap size programatically. The AdvancedMapViewer has been successfully tested on devices with only 16 MB heap size (like for example the Samsung Galaxy i7500). The original issue was most likely caused by a bad map file with too large blocks. If the crash happens during zooming in or out, it has nothing to do with the launch mode of the activity. I see no reason why we should set the AMV to "singleTask". The official manual ( http://developer.android.com/guide/topics/manifest/activity-element.html#lmode ) also emphasizes that this value should not be used under normal circumstances: When you leave the AMV - for example by going to the home screen - and then later come back to it, the already running AMV instance is used, thus no RAM is wasted. |
|
From tdh...@gmail.com on May 14, 2011 06:24:34 Hmm it seems you are right - there is no need to change the task. I found what caused the problem: Normally if you start the app press home, and start it again, it just goes back to the same activity as you would expect. However if you start the app from Eclipse on the phone, then press home, and start the app again, it creates a new activity on the top of the task. Press home again and start it again and adds another activity to the stack! When you press back several times it pops all the activities off the stack, and if you pop them all, it subsequently works correctly. |
|
From thilo.mu...@gmail.com on May 15, 2011 03:36:50 If it is neither a bug in the AdvancedMapViewer nor the map library, we can close this issue. However, i cannot reproduce the Android behavior you are describing. I have created a simple test application (see attachment) and tried the following:
Result: the application is not reinstalled (as the APK has not been changed). A new activity is not created, instead it just resumes the existing one and i see the following message in the Eclipse console: If i run the application in step 3) via the Android launcher menu in my phone, the result is the same except that no warning message is printed in the Eclipse console. I even tried it with compiling the application against different versions of the Android API (3, 4 and 10), but the result was always the same. So as far as i can see, Android behaves correctly. I assume that there is a bug in your application that causes the problem. Status: Fixed Attachment: Foo.java |
From hansgeor...@gmail.com on March 29, 2011 14:25:49
What steps will reproduce the problem? 1.I extented OverlayMapViewer to show polygons ( see attached files)
2.looks like that more the 6 polygons on the map cause the exception 3. What is the expected output? What do you see instead? 03-29 14:14:52.906: ERROR/dalvikvm-heap(16049): 1390080-byte external allocation too large for this process.
03-29 14:14:52.929: ERROR/GraphicsJNI(16049): VM won't let us allocate 1390080 bytes
03-29 14:14:52.933: DEBUG/dalvikvm(16049): GC_FOR_MALLOC freed 0K, 46% free 4484K/8263K, external 23529K/25577K, paused 16ms
03-29 14:14:52.933: DEBUG/AndroidRuntime(16049): Shutting down VM
03-29 14:14:52.933: WARN/dalvikvm(16049): threadid=1: thread exiting with uncaught exception (group=0x40015560)
03-29 14:14:52.937: ERROR/AndroidRuntime(16049): FATAL EXCEPTION: main
03-29 14:14:52.937: ERROR/AndroidRuntime(16049): java.lang.OutOfMemoryError: bitmap size exceeds VM budget
03-29 14:14:52.937: ERROR/AndroidRuntime(16049): at android.graphics.Bitmap.nativeCreate(Native Method)
03-29 14:14:52.937: ERROR/AndroidRuntime(16049): at android.graphics.Bitmap.createBitmap(Bitmap.java:477)
03-29 14:14:52.937: ERROR/AndroidRuntime(16049): at org.mapsforge.android.maps.Overlay.setupOverlay(Overlay.java:362)
03-29 14:14:52.937: ERROR/AndroidRuntime(16049): at org.mapsforge.android.maps.MapView.onSizeChanged(MapView.java:1813)
03-29 14:14:52.937: ERROR/AndroidRuntime(16049): at android.view.View.setFrame(View.java:7242)
03-29 14:14:52.937: ERROR/AndroidRuntime(16049): at android.view.View.layout(View.java:7169)
03-29 14:14:52.937: ERROR/AndroidRuntime(16049): at android.widget.FrameLayout.onLayout(FrameLayout.java:338)
03-29 14:14:52.937: ERROR/AndroidRuntime(16049): at android.view.View.layout(View.java:7175)
03-29 14:14:52.937: ERROR/AndroidRuntime(16049): at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1254)
03-29 14:14:52.937: ERROR/AndroidRuntime(16049): at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1130)
03-29 14:14:52.937: ERROR/AndroidRuntime(16049): at android.widget.LinearLayout.onLayout(LinearLayout.java:1047)
03-29 14:14:52.937: ERROR/AndroidRuntime(16049): at android.view.View.layout(View.java:7175)
03-29 14:14:52.937: ERROR/AndroidRuntime(16049): at android.widget.FrameLayout.onLayout(FrameLayout.java:338)
03-29 14:14:52.937: ERROR/AndroidRuntime(16049): at android.view.View.layout(View.java:7175)
03-29 14:14:52.937: ERROR/AndroidRuntime(16049): at android.view.ViewRoot.performTraversals(ViewRoot.java:1140)
03-29 14:14:52.937: ERROR/AndroidRuntime(16049): at android.view.ViewRoot.handleMessage(ViewRoot.java:1859)
03-29 14:14:52.937: ERROR/AndroidRuntime(16049): at android.os.Handler.dispatchMessage(Handler.java:99)
03-29 14:14:52.937: ERROR/AndroidRuntime(16049): at android.os.Looper.loop(Looper.java:123)
03-29 14:14:52.937: ERROR/AndroidRuntime(16049): at android.app.ActivityThread.main(ActivityThread.java:3647)
03-29 14:14:52.937: ERROR/AndroidRuntime(16049): at java.lang.reflect.Method.invokeNative(Native Method)
03-29 14:14:52.937: ERROR/AndroidRuntime(16049): at java.lang.reflect.Method.invoke(Method.java:507)
03-29 14:14:52.937: ERROR/AndroidRuntime(16049): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:839)
03-29 14:14:52.937: ERROR/AndroidRuntime(16049): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)
03-29 14:14:52.937: ERROR/AndroidRuntime(16049): at dalvik.system.NativeStart.main(Native Method)
03-29 14:14:52.937: WARN/ActivityManager(109): Force finishing activity org.mapsforge.applications.android.samples/.OverlayMapViewer
03-29 14:14:53.437: WARN/ActivityManager(109): Activity pause timeout for HistoryRecord{406f03a0 org.mapsforge.applications.android.samples/.OverlayMapViewer}
03-29 14:14:53.453: VERBOSE/RenderScript_jni(197): surfaceCreated What version of the product are you using? On what operating system? Latest version of mapsforge code and map version 0.2.1, Nexus S Please provide any additional information below. I tried also map version 0.2.2 but even less polygons led to the exception
Attachment: OverlayMapViewer.java bw01.dat bw02.dat bw03.dat bw04.dat
Original issue: http://code.google.com/p/mapsforge/issues/detail?id=112
The text was updated successfully, but these errors were encountered: