New Bug when initiatiating a new map download

tkansgar shared this problem 25 days ago
In Progress

Hi,

I currently use version 3.36.2 (on Samsung Galaxy A3 (2016) with Android 7.0). And since this version I observe a new strange behaviour when initiatiating a new map download:

  1. Go to the online maps screen.
  2. Choose "4UMaps" and in the right hand menu of "Outdoor" choose "Download"
  3. Choose "Current view" ("Aktuelle Ansicht" in German).

At this point normally the screen for adjusting the download parameters appeares. But now in most cases the screen gets black for two or three seconds, then the online maps screen appears again.

  1. Again choose "Download" at "4UMaps" -> "Outdoor".
  2. Again choose "Current view".

Now the expected parameters adjusting screen appears, but the track lines normally visible on the small map section on top of the screen are missing.

  1. Under "Download type" choose "Expand existing map (SQL)".
  2. Choose the desired existing map.
  3. Check "Overwrite older map tiles".
  4. Enter an amount of days.
  5. Tap on the refresh button to count the map tiles to download.
  6. Tap on the "Download" button.

Map download starts as expected, but beneath the download progress dialog there is another progress dialog visible, which is the same one, when starting Locus Map, ending with the track lines to display (those, which were missing before on the parameters adjusting screen). The map download itself is successful then. And the other (normally not displayed) progress dialog dispears too.

I think, this happens more often, when my tracks database grows.

Can you reproduce this strange behaviour?

Best regards

tkansgar

Comments (8)

photo
1

Good day tkansgar,

thank you for very precise bug report, appreciate it!

Not sure if this may be related to the size of your track database > should not. Anyway, the problem is clearly in exactly this point: "in the most cases the screen gets black for two or three seconds, then the online maps screen appears again.". It looks like Locus Map is terminated and automatically restarted.

May you, after this happen, try to create a log by this method? I believe that in the log may be useful information, what happens on the background. Thank you and sorry for these complications!

Menion

photo
1

Hi Menion,

I just sent the Android bug report to you. Hope you can find the bug.

Best regards

tkansgar

photo
photo
1

Hi Menion,

how is the status here? Did my Android bug report help you analysing the crash?

Best regards

tkansgar

photo
1

Hello tkansgar,

sorry for the delay in my answer.

I was precisely analyzing received log (thanks for it), but unfortunately, I'm unable to find there any clear reason why app crash to you when you start map download. There seems to be one small problem with one internal library, but this lib does not have any new version and also no other users reported these weird crashes.

I'll be watching this, but without the clear crash in the log, I'm unable to fix this problem. So I suggest to wait to next Locus Map version (most probably next week) and give it a try. Maybe some magic appears and the problem will be solved. Otherwise, we may give a try to log once again. Thanks.

photo
1

Hi Menion,

do I understand you correct? You couldn't locate the crash in my bug report? What a bummer! Can I help you in any way to analyse it further on my device?

Best regards

tkansgar

photo
1

Hi Menion,

perhaps I have a useful info for you: I always use the actual map section on the screen to specify the download area. And the probability of the crash seems to be relatively to the zoom level of the map section. If the lowest zoom level of the map tiles to download is 7, the crash never happens, if it is 11, the crash happens almost each time. May be this could help you to locate the bug.

Best regards

tkansgar

photo
1

Good day tkansgar,

thanks for additional information. I'm trying to simulate it on two devices, but no success so far. I'm also checking steps in the source code that follow after a tap on "Current view" option, but there is nothing special that should cause this problem.

We will publish the new Locus Map version during the next days, so please try version 3.37. If there will still be a problem and you will be interested in fix, I will have to create a special version that will print us more information into the log.

Menion

photo
1

Hi Menion,

that sounds like a good plan. I will try the new version, as soon as it is available.

I'm a software developer too. And based on my experience I would suppose, that there is an unitialised (new?) variable at those steps you checked, that causes the crash. And perhaps you know unitialised variables can have another value on other devices than your's. Just an idea of mine. Please keep in mind, that the crash didn't happen in versions before 3.36.2.

Best regards

tkansgar