On 08/24/2018 06:37 AM, [email protected] wrote:
The map itself usualy works without problem. It's when the SQLite map
was in use and you try to select another one: Osmand just hang. I
think it's trying to update the database with new downloaded tiles.
The "wal" file created is write-ahead logs. The "shm" is a shared
memory file used to index the "wal" file. What probably happen is
that change to the database content (ie new downloaded or updated
tiles) are stored in the wal file and when you try to select another
map, all the changes are commited to the SQLite file.
If tiles can't be downloaded or if Osmand doesn't automatically try to
download new tiles, there won't be problem. I don't know if Osmand
will try to automatically download missing or updated tiles for an
underlay/overlay. But for the map itself, it try to do it.
If that's the problem, then there's something somewhere in the code
that's failing to close a database transaction, or perhaps it's trying
to run the entire session as a single transaction. If the code isn't
trying to pass the ACID test (Atomic, Coherent, Isolated, Durable
transactions), maybe turn on autocommit?
Continued database activity on an unclosed transaction will indeed
result in the WAL growing without bounds; it holds the data needed to
roll back the transaction if it fails.
--
You received this message because you are subscribed to the Google Groups
"Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
