Viking 1.3 received a small adjustment to try to improve the auto drawing
stability!
However it looks like there is still a contention between the background
thread(s) and the main thread in updating the display - actually just in the
statusbar readout, as the background thread(s) want to report how many items
are still outstanding to download.
I have had this happen to me just once or twice relatively recently (with lots
of heavy usage). But for me at least, this is much improved stability over the
1.2 and earlier versions.
It appears unfortunately for you possibly because of the large number of active
threads increasing the chances of triggering this race condition clash. (I
suppose when one builds up a large disk map cache over time from a lot of use,
then downloading lots of new tiles doesn't happen quite as often).
Since the race conditions seems to be in statusbar readout, I suggest as a
workaround to try hiding the statusbar (press F12 or View->Show->Show
Statusbar) as this may prevent this clash in the statusbar update since it is
not shown!
I've yet to determine the best way to solve this race condition but I'm hopeful
of figuring something out soon.
Thank you for the detailed bug report.
Be Seeing You - Rob.
If at first you don't succeed,
then skydiving isn't for you.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
