27 points speckx 52 minutes ago 5 comments
perching_aix 13 minutes ago | parent
If you have two apps, both maps...
> The reason behind it is the hardened memory allocator, which seems to create a significant overhead for Osmand. That might be because scrolling a map requires constant loading and discarding of data.
... is this really the right hunch, over e.g. the OpenStreetMaps app lacking in discipline with its heap allocations?
himata4113 4 minutes ago | parent
Seems unlikely, it's java so this is likely related to loading large amounts of objects and having the GC thrashing.
pjmlp 11 minutes ago | parent
Maybe the actual solution is to improve, replace the application.