Higher memory usage (possible memory leak)?

[Andrew Heard]

OAM V5 mostly with Karl Chick's Ordnance Survey (OS) map theme.

[Menion]

I was testing it a lot over the weekend and there seems to be a problem with map tile images (so directly bitmap images)  remaining in the native memory.

The most simple test is to have a NMEA file for simulation, zoom in a lot, so the map move also. Navigation and also track recording seems to be without a problem. Now I have to find out why this happens ...

[balloni55]

Hallo menion,
long time nothing heard from you on this problem

it seems to me that since the V4map change, the problem has worsened.
Today after about 2.5 hours 1.7GB were used by Locus

[Menion]

Ah, thanks balloni for the reminder ... visible truth is that I've forgot about it. I remember I tested it and noticed a very similar (not so critical) problem, but even after some testing, I wasn't able to find out why this happens.

Hmm ... complicated problem.

I may only add it higher in the never-ending list of priority tasks.

[balloni55]

visible truth is that I've forgot about it.

sorry, i can't forget it....
after ~ 2.5 hours locus first becomes very slow and then it grinds

[Menion]

Hi balloni,
I've finally yesterday and today made some tests and found only a single problem that was caused by using the auto-zoom feature. Are you using it?

[balloni55]

that was caused by using the auto-zoom feature. Are you using it?

no, never sorry. Only manual zoom in/out
the problem results exclusively from loading new map tiles

[ThomasD.]

Sadly, this behaviour continues in 2024. I mentioned it last year here. Did my first longer motorcycle day trip for this year and what happened: Locus crashes. Worse! App freeze after 2.5 hours, then it close itself.

I have gold abo, newest LoMaps, Sunny 1" SRTM with shading activated, Autozoom enabled and was navigation a route planned with Locus Routeplanner about 250 km.

Please fix this issue. I use Locus Maps since 2018 for motorcyling with thousands of kilometers and never had this issue since last year.

[michaelbechtold]

I have the same impression, although from another scenario. Locus running in the background as a service basically 7 x 24 (even when not out of the house), over time it will eat up memory. This makes some popup menus pure white. Most of the cases it recovers some time later, but sometimes I need to restart Locus to get it back "on track".
As memory leaks are one of the hardest things to catch in development, I recommend to switch off shading while traveling. For planning I understand shading is very helpful. While "executing" it's not, for sure not when you go 100 mph + :-)))
Anyway, just my 2c, trying to "buy time" until resolution, which might take quite some time.
Cheers
Michael

PS: I am not claiming that shading IS the culprit, but for sure it is a load for battery and memory alike, hence low hanging fruit - without guarantees, though ...

[ThomasD.]

My configuration (except better Hardware) has not changed. So it's a Locus failure.

[michaelbechtold]

I did not dispute that - I thought and wrote about a practical chance to ease pain a bit for the time being.
Analysis and fix has to be on Locus side for sure.

[ThomasD.]

Analysis and fix has to be on Locus side for sure.

One year passed - result?

[Menion]

Confirmed today during a ride to work ... 45 minutes till the system killed stucked Locus. I have to look at it more carefully soon.

[michaelbechtold]

That's a brutal one ...
I very rarely had a crash related to memory in more than 10 years, but blank popup menues and screens and alike have been a regular issue.
Hence I suspect there might be more than one leak OR one root cause leak that develops towards different, more or less serious consequences, based on still unknown conditions.
Good luck!!
Cheers
Michael

[ThomasD.]

45 minutes? Than I am lucky with 2,5 h  Thanks for looking at this, Menion.