Higher memory usage (possible memory leak)?

[Andrew Heard]

No obvious memory leak in 4.23.0 here.

• Initial memory 153 MB
• 15m later 154 MB
• 7h later 211 MB (after tracking recording)

[balloni55]

@Andrew Heard
what map and theme do you use?
which zoom range?
with map rotation?

[michaelbechtold]

- map shading?
- dynamic elevation?

[Menion]

Track recording causes no problems. My test setup used an active navigation with many recalculations (maybe 30+ during a 45 min ride). So I believe it will be connected. Anyway, I promise I'll look at it during the next weeks ...

[Andrew Heard]

@Andrew Heard
what map and theme do you use?
which zoom range?
with map rotation?

- map shading?
- dynamic elevation?

• 2021-11-28 OpenAndroMaps Australia-Tasmania
• 200m (on ruler) (whatever ZL that is I don't generally view)
• map rotation:on
• track recording:on
• navigation:off
• map shading:off
• dynamic elevation:off
• display is normally off (99.99% of recording time)

[Andrew Heard]

Wrong topic I know, sorry, but charts below (time vs. battery current milliamps each 2 minutes) comparing Locus with just track recording vs. Locus with navigation and track recording. Just thought it was interesting & confirms for battery misers when riding all day why avoiding navigation mode could wring out the life of the battery before it goes flat. Ignore the -250mA spike on the 1st chart - was when camera used, not just Locus running. I have found/ discovered recently that measuring/ logging current with Tasker rather than %level is a better indication of energy usage. At 10:45 in 2nd chart, navigation stopped and was then just track recording.

@menion- I note in v4.23.1 release notes "reduced app refresh in the background when not active" - charts below are for 4.23.0 so would be interesting now to see whether this affects the battery current. Did you make this change to save battery energy?

see more measurements in post https://forum.locusmap.eu/index.php?topic=8855.msg75438#msg75438

[Menion]

New Beta just published and the issue that caused memory problems on my own device should be fixed now!

https://forum.locusmap.eu/index.php?topic=8855.msg75429#msg75429

Give it a try please, thanksů

[balloni55]

Hello menion
unfortunately nothing has changed for me after 1.5 hours 1GB is occupied

[Menion]

Hmm, consumed memory itself is not a problem. The problem is if this slows down your system and the app.

Is this still happen to you? And still even only during common usage as moving an OAM (TOTM theme) map and nothing special. No recording, no navigation, live tracking, etc?

I made many 3-hour tests with various parameters and even basic movement of the map in zoom level 16 cased no problems. Maybe I should try also OAM maps and this specified theme ...

[ThomasD.]

I am sorry that I was not able to test this in the mean time. Will give it a try in my 3 weeks motorcycle trip in june. First day will be more than 8h of riding - this should be a good test.

[Andrew Heard]

Hmm, consumed memory itself is not a problem.

I'm unable to test at present (cycle touring) but continually increasing memory consumption (leak) would eventually become a problem. Sometimes the leak is so slow (bytes over days) in practice won't matter (like prostate cancer).

[balloni55]

Hello menion
I have been testing different settings over the last few days and have noticed the following.
For me the problem occurs both with
OAM and TOTM theme
as well as with
Lomap and hike§bike theme
when the map rotation is activated.

If I set the map orientation to north up, the problem does not occur.

Example: hiking biking ZL16-18
I start locus with the map orientation set to north up then memory of 180 +-20MB is used no matter how long locus runs.
If I switch on map rotation, the amount of memory used increases. After half an hour approx. 400MB.
If I switch back to map orientation north, the used memory volume remains in this range

maybe this info will help you

[ThomasD.]

New Beta just published and the issue that caused memory problems on my own device should be fixed now!

https://forum.locusmap.eu/index.php?topic=8855.msg75429#msg75429

Give it a try please, thanksů

This version is ever more worse than before. Crashes every 1h! Tried to disable hillshading, but nothing changed.

@Menion: I am on a 3 weeks motorcycle trip and I am willing to test new beta versions day by day. It is really not satisfying to stop every hour to get this app running again, but if you want - you have got a beta tester for the next weeks.

I really want to get Locus running for my needs. It is my favorite navigation app, espacially because of it´s database. And I don´t understand why things have become such worse since LM3.

[ThomasD.]

Ok, for this year I get rid of this useless application called Locus. Going back to Osmand. However I hope you will fix this problem. Looking back here in 1 year. Have a cup of coffee for the wasted money I spend for "Gold". "Gold" - LOL.