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 3 hours ago | parent [-]

Seems unlikely, it's java so this is likely related to loading large amounts of objects and having the GC thrashing.

	▲	someonebaggy 41 minutes ago \| parent \| next [-]
		C++ memory allocator choice probably wouldn't affect Java code, which has its own heap algorithms.
	▲	RedComet 2 hours ago \| parent \| prev [-]
		The core is C++ afaik.