search

QuintinZhangQQ / osmdroid

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

OSMapView SampleExtensive crashes when bitmapsize exceeds VM budget #9

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Hallo,
after zoom into the map (quickly) following exception killed the app:

07-14 18:13:29.101: INFO/OPENSTREETMAP(733): Rendering overall: 15ms
07-14 18:13:29.241: DEBUG/dalvikvm(733): GC freed 1931 objects / 1444312
bytes in 110ms
07-14 18:13:29.281: INFO/OPENSTREETMAP(733): Rendering overall: 4ms
07-14 18:13:29.321: ERROR/dalvikvm-heap(733): 262144-byte external
allocation too large for this process.
07-14 18:13:29.321: ERROR/(733): VM won't let us allocate 262144 bytes
07-14 18:13:29.331: WARN/dalvikvm(733): threadid=93: thread exiting with
uncaught exception (group=0x4000fe70)
07-14 18:13:29.331: ERROR/AndroidRuntime(733): Uncaught handler: thread
pool-13-thread-2 exiting due to uncaught exception
07-14 18:13:29.361: INFO/OPENSTREETMAP(733): Rendering overall: 4ms
07-14 18:13:29.381: ERROR/AndroidRuntime(733): java.lang.OutOfMemoryError:
bitmap size exceeds VM budget
07-14 18:13:29.381: ERROR/AndroidRuntime(733):     at
android.graphics.BitmapFactory.nativeDecodeByteArray(Native Method)
07-14 18:13:29.381: ERROR/AndroidRuntime(733):     at
android.graphics.BitmapFactory.decodeByteArray(BitmapFactory.java:308)
07-14 18:13:29.381: ERROR/AndroidRuntime(733):     at
android.graphics.BitmapFactory.decodeByteArray(BitmapFactory.java:321)
07-14 18:13:29.381: ERROR/AndroidRuntime(733):     at
org.andnav.osm.views.util.OpenStreetMapTileFilesystemProvider$1.run(OpenStreetMa
pTileFilesystemProvider.java:117)
07-14 18:13:29.381: ERROR/AndroidRuntime(733):     at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:6
48)
07-14 18:13:29.381: ERROR/AndroidRuntime(733):     at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:673)
07-14 18:13:29.381: ERROR/AndroidRuntime(733):     at
java.lang.Thread.run(Thread.java:1058)

Original issue reported on code.google.com by surealmn@gmail.com on 14 Jul 2009 at 4:18

GoogleCodeExporter commented 9 years ago 
I see this as well, quit often.

Original comment by carsten....@gmail.com on 2 Nov 2009 at 11:19

GoogleCodeExporter commented 9 years ago

Original comment by neilboyd on 5 Mar 2010 at 8:27

GoogleCodeExporter commented 9 years ago

Original comment by neilboyd on 11 Mar 2010 at 6:31

GoogleCodeExporter commented 9 years ago

Original comment by neilboyd on 11 Mar 2010 at 6:32

GoogleCodeExporter commented 9 years ago 
Revision 110 contains some changes intended to help this issue.

Original comment by neilboyd on 14 Mar 2010 at 7:25

GoogleCodeExporter commented 9 years ago 
And revision 117 seems to have really fixed it.

Original comment by neilboyd on 18 Mar 2010 at 8:58

GoogleCodeExporter commented 9 years ago

Original comment by neilboyd on 19 Mar 2010 at 7:50

GoogleCodeExporter commented 9 years ago 
Hi Neil.

I see this bug fixed but lately I moved to the 3.0.8 build and I am 
experiencing the same issue. Even just opening the map view, I see that after a 
while of inactivity, if I open the app again it goes into out of memory. Did 
something change? Should I change some config in Android?

Thanks a lot!
Armando

Original comment by arma2...@gmail.com on 5 May 2012 at 12:33

GoogleCodeExporter commented 9 years ago 
Please could you attach a stack trace

Original comment by neilboyd on 6 May 2012 at 7:44