Locus slows down and eventually crashes when going off route

Hi Jon,

what router and routing profile do you use? Please, check it in settings > navigation > router.

Hi Michael,

I use Lorouter offline.

Thanks, could you please also send a GPX of a route that makes such problems recalculating? What routing profile do you use? What priority? Route or point/destination?

I used a mix of Touring and Economical - the router tends to get the traffic levels wrong in India and classes very very quiet roads as busy and avoids them for cycling. To get round this I use economical where necessary.

Route priority at 100m

This doesn't just happen in India though. I had it happen a few times last summer in the UK and I would only have used the cycling profile there.

The main issue with it is that you aren't aware it's crashed, so you can quite easily cycle on for a few Kms before thinking I better check the map and you find the app closed.

Hope this helps.

Hi Jon,

thanks for the sample route. Unfortunately, we are unable to replicate the issue and nobody else has reported a similar one. Could you please make a bugreport when the app crashes again? See how to do it: https://docs.locusmap.app/doku.php?id=manual:faq:how_to_create_debug_log. Thanks.

I have to say I noticed this as well. In my case, when navigating at premade track, where I had to take a different route from the track for some parts? This tended to make the app slow and/or crash.... When I notice it in time restarting the navigation seems to help. Using Lorouter offline, route priority, strict route following (I usually want to follow the premade track as closely as possible, but sometimes you need to deviate quite a bit, hence these settings).

What phone are you using letlesAai? I'm on a Samsung S21 Ultra and wondered if perhaps it was hardware related?

I also had it happen again today, but didn't notice until I was well off route. Locus doesn't always notify you correctly of turns in India, so if it thinks the road bends around to the right but it is in fact a t junction you can go sailing on and then when you check the app it's closed. Unfortunately it's 37C here at the moment and the last thing I want to do is wait 15 minutes creating a debug report before I can get back underway. I'll have to wait until it's cooler or a shorter ride before I do that.

And again today, fortunately as we diverted off the track to a cafe so I was able to send a bug report via email.

Hi Jon,

thanks for the bug report sent in a private ticket. Its analysis revealed that the operating system goes "out of memory" due to Locus Map and kills it - this can be prevented by activating only such routes/tracks and points that you actually need for the activity. When too much data is activated, the app loses performance. Otherwise, we couldn't find anything else that would cause the app to crash.

regards

Michal, Locus team

Hi Michal,

Thanks for the reply and update. I've noticed how having many tracks visible slows Locus down for a while and I don't keep many visible anymore. I've also hidden my POI too to be safe.

I'll retest this with only the current track visible, how many tracks can Locus handle open? My tracks are usually under 85km and I'd have may be 4 open if I hadn't been tidying up and hiding them. Would that have caused the memory issue?

Is there any other area that memory could be lost through my settings?

Many thanks.

Jon

Perhaps I should add that I have well over 250 tracks not visible and a few thousand POI's not visible too. Would that number have any affect?

Hi Jon,

tracks or point in the database that are not displayed on the map screen do not affect the app's performance. A few other factors do, see more at https://docs.locusmap.app/doku.php?id=manual:faq:locus_performance.

That's helpful thank you. I've got 16gb of RAM, would other apps using the RAM affect it too? I do use layers a lot though so think this may be half the problem. Strava heat maps in India is extremely useful along with Google maps.

Hi Jon,

we are very sorry but after days of testing and analyzing, we can't find anything that could cause the crash and memory leakage. We've dealt with this kind of issue before (some 2 yrs ago) with another user but again, without any result. Fortunately for other users, this issue is so rare. Unfortunately for you, we can't find a solution. I can offer you a refund of your Premium subscription.

Today I turned off recalculation, used Google maps as my main map with Strava heat maps as an overlay and went off route many many times. It would usually have crashed for each of these extended deviations, but happily carried on with no problems all day.

It's obviously the recalculation that's causing the issues..

Yes it resumed fine today.

Hi guys,

in the next app version, I believe this problem will be (finally) fixed. The issue was indeed caused by the incorrect setup of the recalculated route and had an effect on the available memory. The new version is planned after two weeks, or it may already be tested in the latest Beta version.