MapView Bug?

[giasaste]

Hi,

I am implementing an app that uses google maps. During debugging I found an interesting error which you can easily repsoduce (i hope) if you test the Hello MapView example from google:

"developer.android.com/guide/tutorials/views/hello-mapview.html"

The error:
If you slide to any direction fast (try diagonal direction), for a period of time you will probably get the following error:

02-28 15:59:42.513: D/dalvikvm(26484): GC_CONCURRENT freed 2K, 15% free 18468K/21639K, paused 3ms+6ms
02-28 15:59:42.692: D/dalvikvm(26484): GC_FOR_ALLOC freed 8K, 15% free 18476K/21639K, paused 13ms
02-28 15:59:42.700: I/dalvikvm-heap(26484): Grow heap (frag case) to 19.601MB for 1560976-byte allocation
02-28 15:59:42.724: D/dalvikvm(26484): GC_CONCURRENT freed 0K, 8% free 20001K/21639K, paused 2ms+2ms
02-28 15:59:45.060: D/dalvikvm(26484): GC_FOR_ALLOC freed 3319K, 20% free 17343K/21639K, paused 14ms
02-28 15:59:45.060: I/dalvikvm-heap(26484): Grow heap (frag case) to 18.495MB for 1560976-byte allocation
02-28 15:59:45.075: D/dalvikvm(26484): GC_FOR_ALLOC freed 2K, 13% free 18865K/21639K, paused 16ms
02-28 15:59:45.138: D/dalvikvm(26484): GC_CONCURRENT freed 2K, 13% free 18870K/21639K, paused 2ms+4ms
02-28 15:59:45.911: D/dalvikvm(26484): GC_FOR_ALLOC freed 1603K, 20% free 17396K/21639K, paused 14ms
02-28 15:59:45.911: I/dalvikvm-heap(26484): Grow heap (frag case) to 18.546MB for 1560976-byte allocation
02-28 15:59:45.942: D/dalvikvm(26484): GC_CONCURRENT freed 1K, 13% free 18919K/21639K, paused 2ms+2ms
02-28 15:59:54.271: D/dalvikvm(26484): GC_CONCURRENT freed 2794K, 19% free 17649K/21639K, paused 2ms+2ms
02-28 15:59:58.497: D/dalvikvm(26484): GC_CONCURRENT freed 856K, 18% free 17880K/21639K, paused 5ms+3ms
02-28 16:00:04.341: D/dalvikvm(26484): GC_CONCURRENT freed 1003K, 17% free 18063K/21639K, paused 4ms+4ms
02-28 16:00:11.083: D/skia(26484): ------- imageref_ashmem create failed <(null)> 131072
02-28 16:00:11.091: D/skia(26484): ------- imageref_ashmem create failed <(null)> 131072
02-28 16:00:11.614: D/skia(26484): ------- imageref_ashmem create failed <(null)> 131072
02-28 16:00:11.614: D/skia(26484): ------- imageref_ashmem create failed <(null)> 131072
02-28 16:00:11.638: D/skia(26484): ------- imageref_ashmem create failed <(null)> 131072
02-28 16:00:11.646: D/dalvikvm(26484): GC_CONCURRENT freed 1097K, 16% free 18222K/21639K, paused 2ms+6ms
02-28 16:00:11.646: D/skia(26484): ------- imageref_ashmem create failed <(null)> 131072
02-28 16:00:11.646: D/skia(26484): ------- imageref_ashmem create failed <(null)> 131072
02-28 16:00:11.646: D/skia(26484): ------- imageref_ashmem create failed <(null)> 131072
02-28 16:00:11.646: D/skia(26484): ------- imageref_ashmem create failed <(null)> 131072
02-28 16:00:11.685: D/skia(26484): ------- imageref_ashmem create failed <(null)> 131072
02-28 16:00:11.692: D/skia(26484): ------- imageref_ashmem create failed <(null)> 131072
02-28 16:00:11.692: D/skia(26484): ------- imageref_ashmem create failed <(null)> 131072
02-28 16:00:11.731: D/skia(26484): ------- imageref_ashmem create failed <(null)> 131072
02-28 16:00:11.739: D/skia(26484): ------- imageref_ashmem create failed <(null)> 131072
02-28 16:00:11.739: D/skia(26484): ------- imageref_ashmem create failed <(null)> 131072
02-28 16:00:11.739: D/skia(26484): ------- imageref_ashmem create failed <(null)> 131072
02-28 16:00:11.739: D/skia(26484): ------- imageref_ashmem create failed <(null)> 131072
02-28 16:00:11.802: D/skia(26484): ------- imageref_ashmem create failed ...............
..........
....

The map crashes. Any idea how to solve this?
Thanks a lot in advance.

Regards,
Ioannis

 

[giasaste]

I tested the Hello MapView example with Samsung Galaxy S2 and with the Galaxy Nexus. Same error all the time.

 

[robvr]

Same here
Tried a lot of workarounds but the problem seems to be in maps itself
Methods like animateTo result in memoryleaks and after a while cause crash of Dalvik.
Explicit calls of system.gc() don't help they don't solve the leak itself.

Anybody a solution?

 

[giasaste]

its strange that it doesn't happen with the google maps app that comes with the phone... at least i cannot reproduce this problem there