Sometimes a "ConcurrentModificationException" occurs when adding markers from multiple threads about android-maps-utils HOT 12 CLOSED

Hey Jonas, this is fixed in head. I will release v0.2.1 soon.

from android-maps-utils.

Any ETA on that release? :)

from android-maps-utils.

Sorry about that. You might have noticed a lack of activity from me :)

I've been swamped while launching this project: http://g.co/santatracker

I'll get to this ASAP. I'll need to make sure any other changes made
between the last release are suitable for a point release.

from android-maps-utils.

No problem, I figured there were more pressing matters :) (PS: Santa Tracker is awesome.)

No problem, thanks for this library! Will there be a bit of a change log for 0.2 -> 0.3?

from android-maps-utils.

Ughhh... Yeah I got this one too... I would like to elaborate more on how the crash happens.
1.) Works well when map is loaded (in a MapFragment).
2.) "Switch" to another activity (non-map) within my App
3.) "Swtich back" to my map Activity ... boom
... My code has a potential to update the markets anytime (called by the host Activity).

from android-maps-utils.

First of all thanks for this library.

I have this issue too. I'm loading my data from a server in batches and call addItems() followed by cluster() each time a new batch arrives. This all happens on the main thread. See here.

It works for a few batches then eventually crashes with a ConcurrentModificationException.

Removing PreCachingAlgorithmDecorator from ClusterController's mAlgorithm property and using NonHierarchicalDistanceBasedAlgorithm directly avoids this issue.

I'm using head (f862ec3). Also tried tag 0.2, but this version has the same issue.

Stack trace:

01-07 21:49:35.841: W/dalvikvm(10120): threadid=30: thread exiting with uncaught exception (group=0xa61f2908)
01-07 21:49:35.841: E/AndroidRuntime(10120): FATAL EXCEPTION: Thread-371
01-07 21:49:35.841: E/AndroidRuntime(10120): java.util.ConcurrentModificationException
01-07 21:49:35.841: E/AndroidRuntime(10120):    at java.util.ArrayList$ArrayListIterator.next(ArrayList.java:569)
01-07 21:49:35.841: E/AndroidRuntime(10120):    at com.google.maps.android.clustering.algo.NonHierarchicalDistanceBasedAlgorithm.getClusters(NonHierarchicalDistanceBasedAlgorithm.java:90)
01-07 21:49:35.841: E/AndroidRuntime(10120):    at com.google.maps.android.clustering.algo.PreCachingAlgorithmDecorator.getClustersInternal(PreCachingAlgorithmDecorator.java:83)
01-07 21:49:35.841: E/AndroidRuntime(10120):    at com.google.maps.android.clustering.algo.PreCachingAlgorithmDecorator.access$0(PreCachingAlgorithmDecorator.java:73)
01-07 21:49:35.841: E/AndroidRuntime(10120):    at com.google.maps.android.clustering.algo.PreCachingAlgorithmDecorator$PrecacheRunnable.run(PreCachingAlgorithmDecorator.java:106)
01-07 21:49:35.841: E/AndroidRuntime(10120):    at java.lang.Thread.run(Thread.java:856)

from android-maps-utils.

@choefele ouch - good catch.

from android-maps-utils.

This should fix that one:
1845be4

Cutting a release today/tomorrow.

from android-maps-utils.

0.2.1 is cut, and uploaded to sonatype. It will hit mvn central soon.

from android-maps-utils.

ba64fb9
7766100

from android-maps-utils.

Sorry for my English.

I've got this exception. I use standard renderer and algorithm (don't customize them).

from android-maps-utils.

Isso pode ser resolvido criando uma nova thread para fazer o while na lista de markers.
Em seguida é só voltar para a UI Thread quando for executar algum ação de UI como mMarker.remove() ou mMarker.setPosition(), por exemplo.

from android-maps-utils.