-
-
Notifications
You must be signed in to change notification settings - Fork 567
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Concurrency issues with map #1706
Comments
Tinkering and pondering on this, I don't think it is strictly related to modifying information on the map but 'modifying' the CacheCache through two concurrent read operations. |
Looking on Market it's new in 2012.06.01 |
@rsudev I have a pull coming up where I split the member search. it is used by multiple runnables which gives me the creeps. |
@mucek4 It occurred in master as well from time to time AFAIK, but no clear reproduction scenario is know to me. Do you have more ideas from support? (Couldn't reproduce the issue from @samueltardieu with the described actions either) |
@rsudev I think you're right about the CacheCache being modified while being accessed. I'm currently making it synchronized, in hope to fix this problem in the next maintenance release, waiting for its total nuke (as proposed elsewhere by @Bananeweizen) + possible rewrite. |
Concurrent modifications could occur, especially on very large displays where we may have to draw a lot of caches at the same time while fetching others. This could lead to ConcurrentModificationException errors, as described in #1706.
@mucek4 The log in the market may be mine (and similar to this one), I pressed "report" when Android prompted me. |
Why is this marked as high ? |
This may be a duplicate, but this may contain new information and updated traces.
On a Galaxy Tab running Android 4.0.4 and c:geo 2012.06.01, moving the live map quickly with a small zoom level and thus containing lots of caches will exhibit several concurrency issues.
It looks like we hide some of them in the logs and do not crash, but are still sensitive to a
ConcurrentModificationException
. We need to understand what thread modifies which information in the map. We cannot modify the overlay information while it may be used by the UI thread, so all the overlays modifications may have to occur through a handler to ensure we are indeed using the UI thread.The text was updated successfully, but these errors were encountered: