Problem with AQM import to PGD

You can post here if you have found a bug or if you are faced to a strange behavior.
Frogfoot
Posts: 9
Joined: Sat Apr 16, 2016 10:23 am

Problem with AQM import to PGD

Post by Frogfoot » Sat Apr 23, 2016 1:33 pm

Hi,
So far very impressed with version 2.
I have been creating AQM format maps using MOBAC for large parts of the UK, at all available zoom levels. For the most part this has gone very well with the AQM files being readable by Alpinequest. I have successfully imported some into the new PGD format (which is great as there is now no loading time even for very large files ~ 10GB) However I then tried to create a map of the whole of the UK at zoom level 3 to 15. The map as you can imagine is very large (20 GB), but Alpinequest reads it OK in AQM format but when I try to import it to PGD the app hangs at the same place each time. I wonder if it is something as simple as an integer overflow (large number of tiles being processed).

I know this is probably not a priority but I thought I would report my findings none the less.

Frogfoot
Posts: 9
Joined: Sat Apr 16, 2016 10:23 am

Re: Problem with AQM import to PGD

Post by Frogfoot » Mon Apr 25, 2016 8:19 pm

A little bit more information, the log cat shows the following

04-25 21:08:05.612 32098 32105 W art : Suspending all threads took: 19.195ms
04-25 21:08:08.892 32098 32108 E AndroidRuntime: FATAL EXCEPTION: FinalizerWatchdogDaemon
04-25 21:08:08.892 32098 32108 E AndroidRuntime: Process: psyberia.alpinequest.full, PID: 32098
04-25 21:08:08.892 32098 32108 E AndroidRuntime: java.util.concurrent.TimeoutException: com.android.internal.os.BinderInternal$GcWatcher.finalize() timed out after 10 seconds
04-25 21:08:08.892 32098 32108 E AndroidRuntime: at java.lang.Object.wait(Native Method)
04-25 21:08:08.892 32098 32108 E AndroidRuntime: at java.lang.Object.wait(Object.java:423)
04-25 21:08:08.892 32098 32108 E AndroidRuntime: at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:101)
04-25 21:08:08.892 32098 32108 E AndroidRuntime: at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:72)
04-25 21:08:08.892 32098 32108 E AndroidRuntime: at java.lang.Daemons$FinalizerDaemon.run(Daemons.java:200)
04-25 21:08:08.892 32098 32108 E AndroidRuntime: at java.lang.Thread.run(Thread.java:818)
04-25 21:08:12.022 4716 4716 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.startService:1305 android.content.ContextWrapper.startService:606 android.content.ContextWrapper.startService:606 com.samsung.android.sm.common.SmartManagerReceiver.b:259 com.samsung.android.sm.common.SmartManagerReceiver.onReceive:107
04-25 21:08:12.032 3523 4201 W ActivityManager: Force finishing activity psyberia.alpinequest.full/.AlpineQuestActivity
04-25 21:08:12.142 3523 4795 E android.os.Debug: ro.product_ship = true
04-25 21:08:12.142 3523 4795 E android.os.Debug: ro.debug_level = 0x4f4c
04-25 21:08:12.142 3523 4795 E android.os.Debug: sys.mobilecare.preload = false
04-25 21:08:12.292 3523 3534 W art : Suspending all threads took: 5.178ms

This looks to me like the Garbage collection thread is being upset by the device going to sleep. Maybe a wakelock is required while importing files.

Tom

Psyberia-Support
Site Admin
Posts: 4895
Joined: Wed Apr 14, 2010 9:41 pm

Re: Problem with AQM import to PGD

Post by Psyberia-Support » Mon Apr 25, 2016 9:34 pm

Hi and sorry for the delay!

I haven't been able to closely look at this problem right now, I'll do it as soon as possible.
Truth is I haven't tested to import very large AQM files, since you can directly read them. But I'll try, check your logs and mine.

PGD maps do not have loading times, but note that if you put your .AQM maps in a writable folder (even in the SD card), there will only be a loading time the first time you select the map, but not after (the app will write an auto-generated index to speed up the following loadings).
Do you like AlpineQuest ? Leave a small comment on Google Play !

Psyberia-Support
Site Admin
Posts: 4895
Joined: Wed Apr 14, 2010 9:41 pm

Re: Problem with AQM import to PGD

Post by Psyberia-Support » Fri Apr 29, 2016 8:44 am

As a (technical) follow up, this problem seems to be the one described here.
You seem to be right when saying that a wakelock could be needed. I'll have a look at this when I have some time.
Thanks for your report and sorry again.
Best regards
Do you like AlpineQuest ? Leave a small comment on Google Play !

Psyberia-Support
Site Admin
Posts: 4895
Joined: Wed Apr 14, 2010 9:41 pm

Re: Problem with AQM import to PGD

Post by Psyberia-Support » Tue Mar 02, 2021 2:16 pm

From version 2.2.8, the application will keep the screen on while importing maps so the system should not interrupt the application and the import process.
So this problem should be fixed.
Do you like AlpineQuest ? Leave a small comment on Google Play !

Post Reply