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
Array index out of bounds exception on map #4611
Comments
Under the above mentioned conditions it keeps happening on nearly each triggered refresh of the live map (by scrolling). |
Still happening with release 2016.03.06 under the above mentioned conditions.
|
Another feedback for the current beta version (2016.11.21-RC):
Users comment: Translation: |
While testing the new cache type parsing on the mp I run into this crash very frequently. (almost on every move of the (Google)map. Log:
Version used: 2016.12.27-RC |
@Lineflyer this is mine new IconDecoder. Will take a look |
The last one shall be ok with #6203 |
I can confirm, that the exception is gone now with the PR #6203 Looking closer at this issue I would say, that the other occurences are unrelated...so I leave this open for now. |
While the post of today had another cause, the initial problem is still there and eems to be a rather big problem for our beta users. There are 16 reports for the 2016.12.09-RC version which is quite much given the fact, that we only have 3000 registered testers and most likely even less people also using it.
|
I tested this behaviour on live map again with 2016.12.28: For me it occures in the logs quite often however it does not produce a crash of c:geo as long as debug logging is switched off. Therefore two questions from my side:
|
Make the lock protecting against concurrent modification of the caches list also guard the super method.
Filing through the crashes for the current RC, this came up again. |
Exactly. The occurence raised also for me. But is only leads to a crash if I have debug logging active....see my posting above from 30.12. |
BTW: I can easily test |
I am sure we already have an issue somewhere with a similar thing (or it is just on Google Play crash reports up to now):
Normally this issue happens after using the live map quite a long time (scrolling, loading, and so on).
However just now I tested 2015.01.11-RC with all available connectors activated and just after some movement of the live map I got the following in the log.
Note: This is no crash at that time, only the exception in the debug log.
The text was updated successfully, but these errors were encountered: