Crash when restoring backup after fresh install
I still wanted to report this reproducible crash:
Install Locus Pro 3.6.x onto a fresh Android phone, from the Google Play Store.
Start it and click through until running, showing some map.
Go to restore and select a backup that is on the SD card in Locus/Backup
Select all tick boxes and restore the backup.
It will come back after some secs indicating it needs to restart.
So restart it.
And then it starts and crashes shortly after, while starting.
After this crash you can start Locus again and it will start nicely, without problems.
Outside of this, Locus never ever crashes. And I use it a lot...
I did not attempt to reproduce this yet with the new 3.7.0.
This is done quite many times as I work with rooted Xperia S phones that I reinstall often with Android 5.0.2 (NAOSP 502).
In that case all partitions are wiped clean, except the SD card content. Maybe that is important.
Plus, outside of this initial restore crash, after this I can restore as many times as I want: it will never crash any more.
When I am reinstalling again I will surely check whether the crash still occurs.
The same problem 
Hi,
thanks for report. Unfortunately method to simulate this problem is not 100% as I understand and also quite a complex. Best is, to remember what happen before crash and mainly! create a log/error message, or send an error to Google directly from crash dialog together with some message. Thanks
Hi,
thanks for report. Unfortunately method to simulate this problem is not 100% as I understand and also quite a complex. Best is, to remember what happen before crash and mainly! create a log/error message, or send an error to Google directly from crash dialog together with some message. Thanks
I just reflashed my Xperia S into Android 5.1 and also tried to reproduce this crash again --> it did not crash this time. My theory is that possibly the changes in that area also fixed this one: http://help.locusmap.eu/topic/on-restore-it-always-asks-for-download-additional-data. It also did not ask to load that additional data.
So this was Locus Pro 3.7.0 on Android 5.1. Works like a charm (just a few minutes of using it this far).
I also (for my first time) looked into the logcat of Android while restoring the Locus backup. The only small thing I see is this one, it is reported 16 times while Locus was starting:
03-15 18:24:20.255 W/PackageManager( 9534): Failure retrieving resources for com.arcao.geocaching4locus: Resource ID #0x0
But this gives no negative effect as all works fine: this Locus installation is obviously including the Arcao app geocaching4locus. I reckon this warning is on that app's account.
Another thing I see is on MySQL:
03-15 18:24:29.562 W/art ( 9534): Long monitor contention event with owner method=boolean o.JI.ˊ(android.database.sqlite.SQLiteDatabase, java.lang.String, int, int, int, int, byte[]) from :4294967295 waiters=1 for 129ms
03-15 18:24:29.692 W/art ( 9534): Long monitor contention event with owner method=boolean o.JI.ˊ(android.database.sqlite.SQLiteDatabase, java.lang.String, int, int, int, int, byte[]) from :4294967295 waiters=2 for 131ms
03-15 18:24:29.738 I/art ( 9534): Background sticky concurrent mark sweep GC freed 77393(2MB) AllocSpace objects, 43(771KB) LOS objects, 11% free, 28MB/32MB, paused 5.751ms total 75.470ms
03-15 18:24:29.765 W/SQLiteConnectionPool( 9534): A SQLiteConnection object for database '/sdcard/Locus/mapsOnline/MapQuest_Classic.sqlitedb' was leaked! Please fix your application to end transactions in progress properly and to close the database when it is no longer needed.
03-15 18:24:29.767 W/SQLiteConnectionPool( 9534): A SQLiteConnection object for database '/sdcard/Locus/mapsOnline/MapQuest_Classic.sqlitedb' was leaked! Please fix your application to end transactions in progress properly and to close the database when it is no longer needed.
But I am not sure whether you want these type of reports.
I propose to, for now, close the original topic on the crash, as it did not occur this time; before, with older Locus, it always occurred.
I just reflashed my Xperia S into Android 5.1 and also tried to reproduce this crash again --> it did not crash this time. My theory is that possibly the changes in that area also fixed this one: http://help.locusmap.eu/topic/on-restore-it-always-asks-for-download-additional-data. It also did not ask to load that additional data.
So this was Locus Pro 3.7.0 on Android 5.1. Works like a charm (just a few minutes of using it this far).
I also (for my first time) looked into the logcat of Android while restoring the Locus backup. The only small thing I see is this one, it is reported 16 times while Locus was starting:
03-15 18:24:20.255 W/PackageManager( 9534): Failure retrieving resources for com.arcao.geocaching4locus: Resource ID #0x0
But this gives no negative effect as all works fine: this Locus installation is obviously including the Arcao app geocaching4locus. I reckon this warning is on that app's account.
Another thing I see is on MySQL:
03-15 18:24:29.562 W/art ( 9534): Long monitor contention event with owner method=boolean o.JI.ˊ(android.database.sqlite.SQLiteDatabase, java.lang.String, int, int, int, int, byte[]) from :4294967295 waiters=1 for 129ms
03-15 18:24:29.692 W/art ( 9534): Long monitor contention event with owner method=boolean o.JI.ˊ(android.database.sqlite.SQLiteDatabase, java.lang.String, int, int, int, int, byte[]) from :4294967295 waiters=2 for 131ms
03-15 18:24:29.738 I/art ( 9534): Background sticky concurrent mark sweep GC freed 77393(2MB) AllocSpace objects, 43(771KB) LOS objects, 11% free, 28MB/32MB, paused 5.751ms total 75.470ms
03-15 18:24:29.765 W/SQLiteConnectionPool( 9534): A SQLiteConnection object for database '/sdcard/Locus/mapsOnline/MapQuest_Classic.sqlitedb' was leaked! Please fix your application to end transactions in progress properly and to close the database when it is no longer needed.
03-15 18:24:29.767 W/SQLiteConnectionPool( 9534): A SQLiteConnection object for database '/sdcard/Locus/mapsOnline/MapQuest_Classic.sqlitedb' was leaked! Please fix your application to end transactions in progress properly and to close the database when it is no longer needed.
But I am not sure whether you want these type of reports.
I propose to, for now, close the original topic on the crash, as it did not occur this time; before, with older Locus, it always occurred.
Thanks for info and good to hear that issue is not reproducible for you anymore. Because you were only one who reported issue during restore of backup, I'm closing this issue as "unsolvable".
About other issues ... these are just, known to me, complains of Locus that something is missing. Nothing serious, but thanks!
Thanks for info and good to hear that issue is not reproducible for you anymore. Because you were only one who reported issue during restore of backup, I'm closing this issue as "unsolvable".
About other issues ... these are just, known to me, complains of Locus that something is missing. Nothing serious, but thanks!
Replies have been locked on this page!