This object is in archive!
Crash when work with map
Closed
Locus is crashing once in a while, when I am just moving the screen around. Now it happened again and I decided to report it and grab the logcat. So hopefully something can be found in there, I need to add that the phone was recently reflashed to Android 8.1 December. Attached the logcat file (I used matlog app). I also allowed the phone to send the Android level feedback. I did that a couple of times before as well.
Files:
2017-12-29-23-3...
The same problem 
Hello,
thanks for a log. Unfortunately as I see, there is some fatal crash (line 7754) when you try open detail of some point. This crash is made in Android core itself so it is usually really hard ( with my skills still almost impossible ) to fix it.
Are you using some custom rom on your device? This is a common case.
It may be also a problem in inner "Web view" component, so check if you have latest version from Google Play ( https://play.google.com/store/apps/details?id=com.google.android.webview&hl=en ).
Hello,
thanks for a log. Unfortunately as I see, there is some fatal crash (line 7754) when you try open detail of some point. This crash is made in Android core itself so it is usually really hard ( with my skills still almost impossible ) to fix it.
Are you using some custom rom on your device? This is a common case.
It may be also a problem in inner "Web view" component, so check if you have latest version from Google Play ( https://play.google.com/store/apps/details?id=com.google.android.webview&hl=en ).
Hi Menion, tnx for the reply. All apps, including webview, are the latest. And yes, it is a custom rom, ABC ROM for Nexus 5X Bullhead. I was expecting a reply like yours, so I will address the ROM guys at XDA. Close this topic then. CU in 2018 !
Hi Menion, tnx for the reply. All apps, including webview, are the latest. And yes, it is a custom rom, ABC ROM for Nexus 5X Bullhead. I was expecting a reply like yours, so I will address the ROM guys at XDA. Close this topic then. CU in 2018 !
Fine, thanks. If there will be something I may help with, let me know. I'm mainly Java developer and these "Native" system errors are still quite a mystery to me :).
enjoy new year,
Menion
Fine, thanks. If there will be something I may help with, let me know. I'm mainly Java developer and these "Native" system errors are still quite a mystery to me :).
enjoy new year,
Menion
I am still suffering from regular Locus crashes. All feels due to the same issue. In Android forums people report it is fixed when installing the latest webview from the store or by installing Chrome: any of these can then be selected as the default webview provider from the Developers settings in Android. However, none of the settings I tried prevented it from crashing now and then. I am just reporting this here so you know of it and it might help others. Maybe it is just my specific setup, with this rom, I dunno. I will flash in the March edition of Oreo soon, so maybe that brings some relief.
I am still suffering from regular Locus crashes. All feels due to the same issue. In Android forums people report it is fixed when installing the latest webview from the store or by installing Chrome: any of these can then be selected as the default webview provider from the Developers settings in Android. However, none of the settings I tried prevented it from crashing now and then. I am just reporting this here so you know of it and it might help others. Maybe it is just my specific setup, with this rom, I dunno. I will flash in the March edition of Oreo soon, so maybe that brings some relief.
Hello,
sorry to hear this. Anyway as I wrote ... problem in system (or WebView) + custom rom = deadly combination for me to solve :/.
Let me know after you try new version of Android Oreo, if this solved your issue. Otherwise, please create me a fresh new log with latest version of Locus Map and your new rom. I'll look at it then more carefully. Thanks!
Hello,
sorry to hear this. Anyway as I wrote ... problem in system (or WebView) + custom rom = deadly combination for me to solve :/.
Let me know after you try new version of Android Oreo, if this solved your issue. Otherwise, please create me a fresh new log with latest version of Locus Map and your new rom. I'll look at it then more carefully. Thanks!
Hi, I am back on this persisting issue. Sorry for that ;)
It is still haunting me and even moved along to my new phone, a OnePlus 3T.
Locus is not crashing as often as on my previous Nexus 5X, but still it does.
Effect is always the same: I am in the middle of operating Locus, moving the map around or selecting some WP: then it suddenly halts, wait half a sec and poof, gone. I cannot imagine I am the single only one that is experiencing this.
OnePlus 3T: running the latest Android 8.1 Oreo August 2018. As you know I never run the bare bones Rom, but an 'improved' one: in this case it is LineageOS with some additional tweaks. This in itself could dismiss this issue from being pursued, but I am convinced we have access to high quality roms made by competent group of developers.
For this issue, in the past months I collected Android logs and shared in the XDA forums hoping for a hint into the right direction. On the previous 5X I have been running pure LineageOS, still had the crashing issue and shared logs with the guys on XDA forums: no response.
Now, on the new OnePLus 3T, I have a comment from a competent developer on a crash yesterday:
https://forum.xda-developers.com/showpost.php?p=77451112&postcount=697
He identified the use in Locus of deprecated app:theme (android <= 7.1) instead of android:theme (android >=8.0)
Maybe that is an angle for the issue. At least I am trying to get a finger behind the issue. Thanks for reading this far ;)
EDIT: added tombstone crash file
Hi, I am back on this persisting issue. Sorry for that ;)
It is still haunting me and even moved along to my new phone, a OnePlus 3T.
Locus is not crashing as often as on my previous Nexus 5X, but still it does.
Effect is always the same: I am in the middle of operating Locus, moving the map around or selecting some WP: then it suddenly halts, wait half a sec and poof, gone. I cannot imagine I am the single only one that is experiencing this.
OnePlus 3T: running the latest Android 8.1 Oreo August 2018. As you know I never run the bare bones Rom, but an 'improved' one: in this case it is LineageOS with some additional tweaks. This in itself could dismiss this issue from being pursued, but I am convinced we have access to high quality roms made by competent group of developers.
For this issue, in the past months I collected Android logs and shared in the XDA forums hoping for a hint into the right direction. On the previous 5X I have been running pure LineageOS, still had the crashing issue and shared logs with the guys on XDA forums: no response.
Now, on the new OnePLus 3T, I have a comment from a competent developer on a crash yesterday:
https://forum.xda-developers.com/showpost.php?p=77451112&postcount=697
He identified the use in Locus of deprecated app:theme (android <= 7.1) instead of android:theme (android >=8.0)
Maybe that is an angle for the issue. At least I am trying to get a finger behind the issue. Thanks for reading this far ;)
EDIT: added tombstone crash file
Now the ROM developer looked at the tombstone which are created when Locus crashes.
https://forum.xda-developers.com/showpost.php?p=77460473&postcount=717
Maybe that an issue with 'libskia' is hinting into the right direction? Copying in the text here:
I'm no app developer, but from the thombstone I'm more sure then before, that the crash (which of course takes down the used webview instance - what else then dieing should poor little webview do, if the parent process dies?) is some rendering with libskia. I doubt it's a sepolicy issue, but just to be sure to really exclude this: can you reproduce the crash with selinux set to permissive?
Maybe this is what we are running into, occasionally:
https://www.reddit.com/r/androiddev/comments/6nsc9l/weekly_questions_thread_july_17_2017/dkeeat5/
Now the ROM developer looked at the tombstone which are created when Locus crashes.
https://forum.xda-developers.com/showpost.php?p=77460473&postcount=717
Maybe that an issue with 'libskia' is hinting into the right direction? Copying in the text here:
I'm no app developer, but from the thombstone I'm more sure then before, that the crash (which of course takes down the used webview instance - what else then dieing should poor little webview do, if the parent process dies?) is some rendering with libskia. I doubt it's a sepolicy issue, but just to be sure to really exclude this: can you reproduce the crash with selinux set to permissive?
Maybe this is what we are running into, occasionally:
https://www.reddit.com/r/androiddev/comments/6nsc9l/weekly_questions_thread_july_17_2017/dkeeat5/
Hello,
you found a most probably biggest unsolved problem in the app. It is something different than before (problems with Web view).
Crash you report in your "tombstone" file is no. 1 in the number of reports on our automatic bug tracker on Google Play and ... we have no idea how to solve it.
It is most probably related to some dangerous handling with map tiles (images), but I've already tried to change many things, disable many micro-optimizations I made over years and no effect. Because I'm not (and no one from our small team) C/C++ developer, we are unable to detect the real source of the problem.
The only solution I see is to rewrite the rendering system of the app, at least more than just some minor changes I made so far. This is planned for the end of this year and I really hope, it will help here!
---
So what to do with it? Because it happens to you regularly, you may try one small test.
In next Beta version (will be published today) may be enabled experimental settings by long click on the main menu button. In this new settings (at bottom of settings list) is an option to "Enabled hardware map rendering". It is enabled by default, so please try to disable it. The map will be slower, but it will tell me little more about this issue. Thanks and really sorry for the trouble.
Hello,
you found a most probably biggest unsolved problem in the app. It is something different than before (problems with Web view).
Crash you report in your "tombstone" file is no. 1 in the number of reports on our automatic bug tracker on Google Play and ... we have no idea how to solve it.
It is most probably related to some dangerous handling with map tiles (images), but I've already tried to change many things, disable many micro-optimizations I made over years and no effect. Because I'm not (and no one from our small team) C/C++ developer, we are unable to detect the real source of the problem.
The only solution I see is to rewrite the rendering system of the app, at least more than just some minor changes I made so far. This is planned for the end of this year and I really hope, it will help here!
---
So what to do with it? Because it happens to you regularly, you may try one small test.
In next Beta version (will be published today) may be enabled experimental settings by long click on the main menu button. In this new settings (at bottom of settings list) is an option to "Enabled hardware map rendering". It is enabled by default, so please try to disable it. The map will be slower, but it will tell me little more about this issue. Thanks and really sorry for the trouble.
I was wondering: can you indicate whether this issue still exists in Android 9? I am thinking of stepping over from 8.1 to 9, and this would be a reason to do so. Looking back over the past weeks, I need to add that crashing did not occur that often, but still it does. I am running the latest Android 8.1, latest webview 71.x.
I was wondering: can you indicate whether this issue still exists in Android 9? I am thinking of stepping over from 8.1 to 9, and this would be a reason to do so. Looking back over the past weeks, I need to add that crashing did not occur that often, but still it does. I am running the latest Android 8.1, latest webview 71.x.
Good day,
I'm checking reports from other devices related to this problem and seems that Android 8.0 and 8.1 has the biggest number of such reports (in percents), anyway difference is not so big. If you planned to to update, do it because I believe it won't be worst, but cannot say that issue is solved in the latest Android.
Sorry to say it.
Good day,
I'm checking reports from other devices related to this problem and seems that Android 8.0 and 8.1 has the biggest number of such reports (in percents), anyway difference is not so big. If you planned to to update, do it because I believe it won't be worst, but cannot say that issue is solved in the latest Android.
Sorry to say it.
Replies have been locked on this page!