New Bug when initiatiating a new map download

tkansgar shared this problem 2 months ago
Solved

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 (13)

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

photo
1

Hi Menion,

the word "unitialised" was a typo. I meant "uninitialised".

I just installed the new version 3.37.1. But the crash remains (in one of five cases, only with zoom level 11 as the lowest one). If you plan to create a special version with more detailed log info, I will stand by for you.

Best regards

tkansgar

photo
1

Hi Menion,

did you fix something? I think, the bug is gone! I just installed the newest version, and it didn't crash any more till now!

Best regards

tkansgar

photo
1

Hello tkansgar,

I would like to write "yes", but ... you maybe know some tasks in life, you have no idea what to do with them. I have to admit, it is similar to this problem. I looked on it few days before 3.37.1, but see no possible problems. Then you wrote to me five days ago that issue remains and till then, I had no time to create a special version or to touch core related to this problem. So it is little surprise that it should be fixed. Interesting is that you are still the only one who report us this problem.

I'll mark this topic as "solved", anyway if issue re-appear, feel free to write here and I'll then try to create some special version. Thanks for your patience!

Menion

photo
1

Hi Menion,

perhaps I have a new hint in this issue: It seems, the crash occures the more often the more track lines are displayed on the map screen. Yesterday I had 58 tracks displayed, and Locus crashed totally (not only the download function), when choosing "Current view". Today I reduced to 48 tracks, and only one of five download function calls crashed again. May be if I would reduce the displayed tracks furthermore, the crash wouldn't occure anymore. But this I didn't test till now, since I had to write down all the tracks I want to display currently.

By displaying the old recorded tracks on tour I can see, wether I was on that path before, where I just are on. Very useful for me!

Best regards

tkansgar

photo
1

Good day tkansgar,

can't imagine why visible tracks should cause a problem here. You may anyway test it by making a complete backup of your content (over menu > more > Backup manager or just manually copy Locus/data/database directory). Then you may hide your tracks and to restore them, just restore a backup or copy content of mentioned directory back. Just be sure you copy the whole directory also with hidden files because these files have information which track is currently enabled.

You also wrote some time ago, that older application version worked correctly, so if this is really a problem, feel free to download and use an older version (downloadable manually from here).

Menion