Locus freezes while importing pocket query

konsumschaf shared this problem 4 years ago
Not a Problem

Version 3.1.2

First seen on 3.1.1


When I import my pocket query to my Cache-Folder Locus freezes in about half of all attempts. I enabled the log-file and last thing there is looks like this:


07-09 20:44:05.287 D/dalvikvm(13260): GC_FOR_ALLOC freed 5849K, 16% free 57659K/68260K, paused 109ms, total 110ms

07-09 20:44:05.727 D/dalvikvm(13260): GC_FOR_ALLOC freed 1989K, 17% free 57113K/68260K, paused 112ms, total 112ms

07-09 20:44:05.837 D/dalvikvm(13260): GC_FOR_ALLOC freed 537K, 17% free 57157K/68260K, paused 83ms, total 83ms

07-09 20:44:10.512 W/SQLiteConnectionPool(13260): The connection pool for database '+storage+emulated+0+Locus+data+database+waypoints_db' has been unable to grant a connection to thread 1 (main) with flags 0x5 for 4.0 seconds.

07-09 20:44:10.512 W/SQLiteConnectionPool(13260): Connections: 0 active, 1 idle, 0 available.

07-09 20:44:14.526 W/SQLiteConnectionPool(13260): The connection pool for database '+storage+emulated+0+Locus+data+database+waypoints_db' has been unable to grant a connection to thread 1 (main) with flags 0x5 for 8.001 seconds.

07-09 20:44:14.526 W/SQLiteConnectionPool(13260): Connections: 0 active, 1 idle, 0 available.

07-09 20:44:18.519 W/SQLiteConnectionPool(13260): The connection pool for database '+storage+emulated+0+Locus+data+database+waypoints_db' has been unable to grant a connection to thread 1 (main) with flags 0x5 for 12.001 seconds.

07-09 20:44:18.519 W/SQLiteConnectionPool(13260): Connections: 0 active, 1 idle, 0 available.

07-09 20:44:22.523 W/SQLiteConnectionPool(13260): The connection pool for database '+storage+emulated+0+Locus+data+database+waypoints_db' has been unable to grant a connection to thread 1 (main) with flags 0x5 for 16.009 seconds.

07-09 20:44:22.523 W/SQLiteConnectionPool(13260): Connections: 0 active, 1 idle, 0 available.

07-09 20:44:26.527 W/SQLiteConnectionPool(13260): The connection pool for database '+storage+emulated+0+Locus+data+database+waypoints_db' has been unable to grant a connection to thread 1 (main) with flags 0x5 for 20.009 seconds.

07-09 20:44:26.527 W/SQLiteConnectionPool(13260): Connections: 0 active, 1 idle, 0 available.

07-09 20:44:30.521 W/SQLiteConnectionPool(13260): The connection pool for database '+storage+emulated+0+Locus+data+database+waypoints_db' has been unable to grant a connection to thread 1 (main) with flags 0x5 for 24.009 seconds.

07-09 20:44:30.521 W/SQLiteConnectionPool(13260): Connections: 0 active, 1 idle, 0 available.


Any ideas?


By the way:


07-09 20:35:30.534 D/dalvikvm(11294): Trying to load lib /data/data/menion.android.locus.pro/.娙왍㗠 0x42a78490

07-09 20:35:30.544 D/dalvikvm(11294): Added shared lib /data/data/menion.android.locus.pro/.娙왍㗠 0x42a78490

07-09 20:35:30.544 D/dalvikvm(11294): No JNI_OnLoad found in /data/data/menion.android.locus.pro/.娙왍㗠 0x42a78490, skipping init

07-09 20:35:30.735 I/BugSenseHandler(11294): Registering default exceptions handler


Are these "Chinese" characters supposed to be there?

Comments (17)

photo
2

Good day,


firstly - chinesse characters looks "funny", but they are OK, there is no problem with them.


About problem - seems Locus is unable to correctly connect to waypoints database. May you please restart your device and try it again? It usually helps if there is any unwanted "lock" on database file.


Anyway to be true, I have no idea why this may happen and never saw. Thanks to you log, I'll try to find if anyone had same problem with database on Android. Thanks!

photo
1

Hi,


just tested with 3.1.3. still freezes every now and then. I restart my device every day, so that does not change this behaviour.


Anything I can do to provide you with more input? Anything I should try?


I filled in the crash report of the device (when the system notices that the process does not react any more), but I am not sure who gets this.


Thanks

photo
2

I'm still searching, but everything leads to some "incorrect usage of database" (by app, not by user). Anyway problem is, that I not changed anything around handling with database during last versions.


May I ask, what Android you use and what ROM? Didn't you changed something important on your device last days, like ROM for example or some other advanced system parameters (available only on rooted devices)?


Also you wrote that "when the system notices that the process does not react any more" - in this case, you see "Wait" or "Close" buttons? What happen when you try to wait a while? No change during few minutes?

photo
2

Last thing changed on my device was an Android Update about 2 weeks ago

Device Samsung S4 active (GT-I9295) (not rooted)

Android Version 4.4.2

Kernel 3.4.0-1429916


I just tried to wait longer (pressed "Wait" five times) but nothing happend.


I tried the same pocket query on another device (Samsung Note 8) works as supposed.


I even tried to clear the whole cache and deleted the folder, still happens.

photo
2

OK, I made a backup on my Samsung S4 active (GT-I9295) and restored it on the Note 8. Importet the same GPX File via GC Live. re-imported it 5 times, device freezes as well. So it does not seam to be and device issue, maybe some rude setup of my Locus?


Is it safe to attach my backup in here or does it contain sensible data?

photo
1

Ah this is good information. Best if I should reproduce it on my device.


Please send it on locus@asamm.com. I'll take care of it. Thank you!

photo
3

I just sent it over...

photo
1

Thank you


data received, tested and ... nothing. All works without any issue (imported quite a lot of times with different settigs).


I'm trying to search about this problem and seems it's not unusuall problem, like here, here, and mainly here . Last link seems to have some useful information.


In all cases, you suffer by deadlock on database, that should be caused by attempt from Locus to access database more then once in same time. Anyway this "import" feature do not do this. It's really limited to single instance.


WHat may cause difference - I saw by import of your backup, that you have enabled "Periodic updates". May you disable them? I don't know which addon you use that there is need for this settings, but try to disable them for a while. It's currently only possibility I see.


It this won't help, I'll have to do for you some testing version that will report into log all requests on database and we will see.

photo
2

I found the trigger: Did you chose to display all the caches?


Locus does not freeze as long as you do not display any caches. If you chose to do so it just needs a few imports to freeze.


I think the map tries to refresh in the background while importing that is what might cause the deadlock.


Workaround for me: Deselect all caches, import daily pocket query, select all caches.

photo
2

Thanks for observation.


I still think that there has some effect also enabled "Periodic updates", but yes, it's possible. Unfortunately even with this, I'm unable to simulate same problem. Weird.


Because you wrote that this firstly happen in new 3.1.1 version, there is only one place, where I did a small chance that may have effect on this.


So I've improved it a little bit and we will see in next version.

photo
1

Just tried to turn of the "Periodic updates", still freezes. (its needed for the Geocaching4Locus Addon).


Do not stick to the 3.1.1. version. That is the version when I first noticed, as I am rather new to Locus I try many different things so it is possible that I just did not trigger it before. And 3.1.1 came rather close to 3.1.0 so it could already been in there.

photo
2

3.1.3 freezes as well - even with "Periodic updates" turned off. :-(

photo
2

Sorry to tell you: Still happens with 3.2.0 :-(

photo
2

Good day,


unfortunately, during all these weeks, I never had problem similar to yours, I'm unable to simulate it in any way and also no one other complain about same problem.


Aren't there any plans on update of your device (new device, new Android version)? This is best possible cure :). Otherwise, I'm sorry, but I see no way how to fix it when I'm unable to simulate this problem.

photo
1

Its fine with me, for I have a workaround. I will not change my phone in the near future and it does not work on my tablet as well, maybe some strange coincident with another app?


BTW: Last last two imports with 3.2.2 did not freeze the phone, I will give it a try, if it freezes again I will switch back to my workaround.


I still love this app its a great tool and I leave my Garmin at home nowadays, I just do not need it any more. :-)

photo
2

It works again, I don't no why, but it does. So fixed for me. :-D


Is it possible, that a virus scanner interferers with the databases? I noticed an update of the scanner and it never happened afterwards.

photo
2

Interesting. Can't imagine that other app may affect work with database of another app. But on Android, everything is possible :).


Anyway I'm really glad it works for you now, because as I wrote, I saw no way how to fix it now. Perfect.