search

zeta243 / osmdroid

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

Tiles not reloaded when pending queue too large #311

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Move around on the map view component (embedded in an activity of your 
choice) very fast. Move to region A, back to B and then back to A. Maybe you 
need some tries to reproduce it. 
2. Sometimes when you get back to Region A you may encounter "loading tiles" 
which will never be replaced by real tiles.

What is the expected output? What do you see instead?

Of course the missing tiles should be replaced by the real tiles.

What version of the product are you using? On what operating system?

OSMDroid 3.0.5

Please provide any additional information below.

The issue is relatively easy to reproduce on a GNEX over 3G due to the 
increased resolution (more tile request are issued). So one of the internal map 
request queues evicts old map tile requests but does not inform an other queue 
about the removal.

I investigated the bug and found the root cause. I will attach two files that 
contain a fix. The fix is a HOTFIX and not intended to be simply merged to the 
main trunk. There is some casting involved, but I have currently no time to 
make this prettier. So there is some porting effort needed.

Basically the missing tiles are not removed from the maptile-loading working 
queues when the pending queue size exceeds. So I added some code that when a 
pending tile request is removed the same request is also removed from the 
working queue. This causes the missing tiles to be reloaded.

Once again: Please be aware that the attached files are not intended to replace 
the existing sources of the trunk! They are coded against a forked version of 
3.0.5.

Original issue reported on code.google.com by dirk.hol...@gmail.com on 14 Feb 2012 at 2:22

Attachments:

GoogleCodeExporter commented 8 years ago 
This seems to be the same as issue 335 and fixed through r1090.

Original comment by osei...@gmail.com on 10 Apr 2012 at 7:30

GoogleCodeExporter commented 8 years ago 
Thanks for the report and the investigation into the issue. This has been fixed 
in r1090. If you have any additional issues please reopen or file a new issue 
report.

Original comment by kurtzm...@gmail.com on 24 Aug 2012 at 5:16