Locus Map crash by zooming on OSM Maps

Hardliner shared this problem 2 years ago
Solved

Hello guys,


i have buy a new smartphone (Lenovo Vibe P1) with Android 5.1.1, and i install Locus and test the functions. I select a Online OSM Map and alway was fine. But i have begin with zooming in the map, Locus crash and was close. I test this with OSM Offline Maps i have the same Issue.


I have make a ne Offline Map the same Issue too.


I tested with my own converted Maps in RMAP Format is all fine. I can zoom without crash. The same is with LoMaps without crash.


why the OSM Maps make problems? Is the Issue on Rendering?


I hope you can help me. I go next weekend on a long bike Tour and i need Locus.


Best Regards

hardliner

Comments (5)

photo
1

Good day Hardliner,

this is very interesting, I don't have any similar report during last months.


Do you have after crash dialog "Locus was closed" with option to send error message? If so, send it now please and write me to comment your name. Otherwise, please create me a log by this method: http://docs.locusmap.eu/doku.php?id=manual:faq:how_to_create_debug_log . Thank you and sorry for a complications.

photo
1

Hello Menion i have send error Message after Locus was closed.


I can reproduce the Error and send the Protocol with my Username


Best Regards

Hardliner

photo
1

Good day Hardliner,

sorry for a delay in response! It has it's reason.

Firstly thanks for a log. Unfortunately in log is some serious issue in Android itself in it's core and I'm not skilled enough to say, where exactly is a problem. Anyway please try just yesterday published version 3.19.0. It is possible that it still won't work. In such case, please close Locus and in any text editor, edit config.cfg file that is in root directory of Locus Map.

In this file is prepared parameter dev_map_layer_reuse_bitmaps=true , so change "true" value to "0" or "false". Then start Locus again. It should help in this case.

photo
1

Hello Menion,


only the new Version not fix the Problem. But i edit the config.cfg and set the Parameter to false the Issue was not existent.

Can you explain how did the parameter make with OSM Maps?


Best Regards

hardliner

photo
1

Hello,

so may I understand, that parameter fixed your problem? Hmm.

In logs were only these information:

  1. backtrace:
  2. #00 pc 00000000 <unknown>
  3. #01 pc 000348bf /system/lib/libhwui.so (android::uirenderer::ResourceCache::incrementRefcount(SkBitmap const*)+14)
  4. #02 pc 0001e561 /system/lib/libhwui.so
  5. #03 pc 0001f3e7 /system/lib/libhwui.so (android::uirenderer::DisplayListRenderer::drawBitmap(SkBitmap const*, SkPaint const*)+6)
  6. #04 pc 000786ab /system/lib/libandroid_runtime.so
  7. #05 pc 000b3be3 /data/dalvik-cache/arm/system@framewo

And because you told me that issue happen only when using maps, I considered that issue may be probably in re-using map tiles during zooming. So this parameter disable it.As I wrote, I'm not perfectly sure why this issue happen and it's weird that you are only one who reported it. So probably any of next updates of your device will solve it.