Higher memory usage (possible memory leak)?

[jordyke]

Hello,

we are experiencing higher memory usage after version 3.54.3 . The memory usage is expanding over the time from 500Mb till all the free memory is used and the complete system crashes (after +-4 hrs off driving). We are experiencing this in the all latest versions; our system is android 11 and has 4GB off ram. the issue was also there with android 10.
As side info: we use Lomaps (offline maps) in combination with a lot off tracks

[balloni55]

I have the same experience with LM4 while geocaching

https://forum.locusmap.eu/index.php?msg=66982

where do you see the memory usage ?
Android settings/Apps/Locus memory?

[jordyke]

@balloni55 depending on device:
Developer settings, running services;
you can try to install an older version and see if you experience the same as us. I think vs 4.3 is somthing like our working version

We don't use geocaching

I am also not sure if the problem started with 3.43, i only know that the newer versions give problems to us (3.6X defenitly)

[Menion]

Hi guys, this sounds like a serious problem. Balloni has this problem with geocaching and without the navigation & jordyke during navigation. So common here is the work with map > zooming & panning right?

I've noted a TODO task and will test it next weeks a little.

[jordyke]

Hello,

is there more info about this?
We tested
-using on-and offline maps (no difference),
-no wps (no difference)
-no active kml (no difference)
-only points and tracks (no difference)
-all settings default (except screen allways on!)
rollback to 3.54.3 seems to solve the 'crash' problem (bus still a pretty high memory usage).

[Menion]

Hi guys,
yesterday was published a new app version. I rewrote one part of the background map system that may have influenced this. Based on my measurement, it helped a little. So give the new version a try please and let me know. Thanks.

[Andrew Heard]

What is the best/ preferred way of measuring for/ reporting of memory leaks?

[balloni55]

@ menion
today on a winter cache biketour (-5°C) i could not notice any improvement, sorry
You cannot view this attachment.

[Menion]

Hmm thanks @balloni55 , 1.1GB, it is still too much. Oki, I'll keep searching next few days/weeks, damn...

@Andrew Heard you may see on ballonis screenshot, simply every app/system setting that display current app consumption.

[Andrew Heard]

@menion - no memory leak here, but my situation was quite simplistic - track recording - after startup 154MB, after track record 220MB, a few hours later with no further use 191MB, next day with no further use 175MB .

[Menion]

Thanks Andrew, appreciate your tests. I'm unable to find the difference because of your/mine usage and how @balloni55 or @jordyke use the app. There has to be some issue, but it is quite hard to find ...

[Andrew Heard]

It sounds like the leak is only with geocaching. I was only using track recording, not geocaching. As a retired programmer I don't miss tracking down memory leaks ;-)

[balloni55]

It sounds like the leak is only with geocaching.

Hello Andrew
no,
memory leak occurs when:
- map is visible
- map is centered
- map is moving (new tiles are loaded)
- map rotate ?
Wolfgang

[Andrew Heard]

ok, in my testing you'd think then that I had all those factors? Or what different should I try to reproduce the leak?

[balloni55]

what map and theme do you use?
i use OAM V5 with TOTM mapsforge