Locus crashing

Thanks for link, didn't know about version archive. I have tried older version, it looked promising but also having same problems.

Currently I had to result to bringing my old phone just for Locus on weekend trip.

Locus is only app having these issues. I can run Strava or mapy.cz without crashing and even without excluding from battery management.

Can we schedule conference call to do test on my phone?

Just give me instruction what to prepare software vise. I'm using Linux on all my computers but can run virtual machine with Windows or borrow spare PC from work if necessary.

Hi Marek,

Pixel have integrated screen recorder.

I have catched 2 crashes. Recordings are in Gdrive on link bellow.

Last week Locus crashed immediately as I loaded particular track or opened route planner. Now these 2 are "working".

Still crashes after moving a bit around map. Just don't have right now scenario where it crashes immediately a every time.

https://drive.google.com/drive/folders/1hLr92VH2B8SwU83OzKgOWy6lOHBm8KIP

Looking to log I see NullPointerExeption. Maybe extra build with enhaced logging to hunt down what is failing?

I can make a trip to meet you for debugging session next weekend. I was planning to ride Brno->Praha for some time anyway.

Your link not working but I installed fresh beta from https://drive.google.com/drive/folders/1t1CYpIhHGZXjNBqOFUPQKTTvddj7VVCv

2 crashes while panning map at 16:31 and 16:32

Log attached.

Weird... Could you please try this link https://drive.google.com/file/d/15NRyCkjnHZoQ_fbK8e3UAmKmL9acVxkh/view?usp=sharing ?

Didn't noticed log is over 2mb limit. Uploaded it here : https://drive.google.com/file/d/109Bxt1nuO68uFfwTMkksfkeXndkEHQaW/view?usp=drivesdk

Still the same. Maybe try set me as person you are sharing file with and let GDrive send me notification.

I already did. Did you receive notification? https://drive.google.com/file/d/1gtjl3t0Ag1QrGJAMOdv7AAFFjFrtYJxY/view?usp=drive_link

I have installed it already at Friday, just busy weekend and didn't got to post it yet.

Friday afternoon/evening. Downgraded back to beta from your link and it crashed while panning the map (sometime after 19:30 if I remember correctly)
https://drive.google.com/file/d/12vitJMf23D2TTXDBaUIY2lSdDwGS56UL/view?usp=drive_link

Saturday morning:
log: https://drive.google.com/file/d/113iTjdg2aWBM-qXlI5-Odg-npEZZ__kz/view?usp=sharing
ride recording, you can find gaps/crashes in Ždánický les behind Bučovice. This is copy of original recording where I trimmed start and finish for privacy: https://link.locusmap.app/t/wea1jk

Today morning, I have been looking at Saturday recording for time of last recorded point before crash when Locus crashed repeatedly.
I have noted these times but me looking into log they don't seem to match log well (time read from WearOS watches paired to phone in question):
8:23
8:25:4X
8:25:58-8:26:00
https://drive.google.com/file/d/13-kRoP4bky1FeHwN4D31VoMiFexo29Dl/view?usp=sharing

I see in your logs same version / API level 14.0 (34).
Difference is that you are on Samsung.
Did it started after system upgrade. For me I had system upgrade and also Locus upgrade in few day between activities. Since I have tried downgrading quite a few versions back, it seems to be about interaction with newer system version.
Tried also legacy Locus 3 with same crashing issue.

Unfortunately log from my SSL issue ticket (previous to crashing issue) don't have the "new start" header with system version at the time.

Hello Marek,

any progress? My offer to debug on my phone still stand. Currently I basically can't use Locus at all. It crashed after a minute tops.

This weekend I'm attending this race and really need working Locus. https://ultrabikers.eu/ub30-berlin-challenge/

I was hoping not have to use the old phone again.

Hi skvedo,

sorry, but we are not able to identify your problem. The last try is to generate bugreport by following this tutorial https://docs.locusmap.app/doku.php?id=manual:faq:how_to_create_debug_log Thank you.

Fresh bug report:
https://drive.google.com/file/d/1AIPoUf7hErOMqGk-JdnTaSj4NgYfoxcS/view?usp=drive_link

One older:
https://drive.google.com/file/d/140B4cUO1qUIiYT4Vlo-5rwhgaeSKCm2e/view?usp=drive_link

I still believe both of my issues are outside of Locus code, but only you can identify what is going on. Also Locus is only app affected for me.

Hi skvedo,

did you repeat the crash several times before generating bugreport?

Hi Marek,

sorry for late response. I was riding the race and recovering from it after.
I believe it has crashed few times before generating report.
In Locus log i see "new start" at:
18:01:16, 18:01:30, report listing 18:06 as generated time

https://drive.google.com/file/d/1F9NQRGPlMHyLfR4LOiWB2bsnLHVMi2VS/view?usp=drive_link

Now I can't make it crash, but it seemed that promising few times already. I will be testing on ride later today.

Noticed in log some issues with backup upload (GDrive full to brim with Locus logs) so disabled backups for now.
Crashes were happening also outside out from wifi coverage, so that shouldn't be that.

Friday 2024-08-30:

last recorded point before crash, first recorded after crash (there might be more, these are really obvious with long flat line):

17:51:15,18:09:17

19:04:01,19:15:30

log file: https://drive.google.com/file/d/1FB2VuQ5ipkT8GH_kNcjU1FibpPdzw5Ff/view?usp=drive_link

Phone mostly not used, just sitting on handelbars recording.

Today 2024-09-02 ~16:53

crashed while panning map to find times listed above
log: https://drive.google.com/file/d/1HqNuZM1Fb4bDmdcgL1z5sqFvy_T7cwXB/view?usp=drive_link

bugreports generated Sunday, Monday morning, Monday afternoon (just after crash):
https://drive.google.com/file/d/1Hrp9hO5cD7Z9Y5kVNPqpGM92XHbrRVz3/view?usp=drive_link
https://drive.google.com/file/d/1HhvqJmFdJ4i288XXyEnvEK-pHk4equ9h/view?usp=drive_link
https://drive.google.com/file/d/1HWiXY1MPFyKwaHgy3xfgD79caTsBxfS6/view?usp=drive_link

Zrovna teď jakýkoliv pohyb po mapě způsobí crash do pár vteřin.

Můžeme prosím dát nějako TS session? Není problém vytvořit Zoom/Teams nebo kdoví co ještě.

Michal

Dobrý den, ve vašem případě je bohužel na vině chyba v nativní systémové knihovně Androidu. Ta se z času na čas vzácně objeví na různých zařízeních. Tu samozřejmě nemůžeme opravit, můžeme vám ovšem nabídnout refund vašeho Premium předplatného. Funkce vám zůstanou aktivní, pokud byste náhodou Locus Map používal na jiném zařízení.

Are my crashes also related to the bug in Android itself (not looking for any refund, I can live with them). Would downgrading to an earlier version of LocusMap help? As also described by Skvedo, earlier versions of Locus did not have the problem.

Helo Blihi,
my attempts to downgrade were not successful. Same issues even in Locus 3 Pro.

@Michal Stupka, @Marek Scholtz is this bug reported/tracked somewhere so I can +1 the issue? I want to continue using Locus. It was working before and is then regression and they should fix what they broke. I would consider warranty the phone because of it (complication as it is company phone).
So far we seen it affects 2 vendors on current system versions. It is reasonable fear it will break on any newer phone.

Since it is a bug deep in Android, it seems to make sense that indeed downgrading does not help. It was worth a try though.

Could you give a hint on where in Android the problem is? Maybe there is something that can be done with the settings (either regular settings or developer settings) to avoid the problem?

I see the text got mixed up...

No crashes happened further on that day, however the next day a crash happened again (in the car, so in navigation mode). I left around 10:00 and the crash happened around 12:18.

Hi Micha,

I already had permissions set to all-time access to the location, and also excluded locusmap from all battery optimization. Google service assisted location had always been switched off.

I use locusmap for nearly a year (more or less daily) without any problems - except these shutdowns that happen only recently.

I'll do my best. It may take a while until I can "catch" a crash.

I'm riding my bike when it happens. The situation might not be such that I can pause to do this time consuming manipulation on my phone - several minutes up to 15 minutes can be long...

Hello again,

I created a bugreport from a crash that occurred yesterday, about 1h/20km after the start.

I hope it will help to get this problem solved.

I cannot attach it here, because it's 42.1 MiB and such exceeds the allowed file size for attachments.

You can find it here:

https://bribre.net/locus/bugreport-2024-09-20-08-44-05.zip

Yes, your description meets what happens on my phone: the app just closes and I don't get any error message nor any notification about what happened.

Thanks a lot for that generosity! For a reason or another, google had taken the double amount from my card, now I'm back on single amount. Such I don't have to discuss with google...

Although you could do nothing from your side to remedy the code error, I got new hope:

Today, my app made an update - who knows, perhaps the problem will not occur any more. I really hope so and can't wait to try it out.

It would have been so good, but I had no luck: The new update of the locusmap app didn't change anything - the app shut down twice (on a 74km ride).While I have no problem to restart the app when using it for navigation, I think I have to look for another app that is more reliable for live-tracking. If anyone has a good tip, I would be thankful.

Hi Blihi, there's no need for more logs. The cause is detected in a "libc" library but maybe it is Locus's bug after all. But extremely hard to detect and investigate. I'm offering a refund to you too, just send me your Locus account address in a private ticket and add a link to this topic.

I appreciate the offer, but there's no need for that. The app is still by far the best out there for what I do with it.

I'm happy to keep supporting it and who knows we can figure out the issue in the future.

@Michal Stupka:

• Even if library libc is the root cause, something must have changed because I observe this issue since maybe 4 weeks but not before.
  
• Observed on Fairpone 3 with Android 10 – so not only new phones or Android versions are affected as assumed in some posts.
  
• Because on my system, no operating system updates were done in last months and Locus 4.26.2 is the only app I observed the issue (also not in Locus 3.70.15): Maybe the function calls from Locus towards the lib have been changed? Or could the lib have been changed by updating aother app?
• Issue happens not only after navigation have been started, but it's most annoying then: In Germany, it's not allowed to operate the mobile while driving, and in other countries it may also be forbidden or at least is a risky action – so you can't restart the routing until you can stop somewhere which can be challenging. In contrast, when laying on the couch and looking at the map, I must only restart Locus and I can do so without any restrictions.
  

FYI, v4.26.3 crashes much more seltem on elsewise unchanged device – even in intense use, it is possible to run Locus a few days without crash, then again several crashes within few minutes.

v4.27.1 crashes much more often – I needed 6-7 tries to delete one point from the DB, navigation is virtually unusable. No issues for several minutes after switching from vector to online map.