I wonder if a website using leaflet.js has better or worse performance in the said case. If it does better, then maybe the problem is on OsmAnd's side?
The fairly obvious answer here is "OEMs don't care about security because very few people will pay for it, either with $ or time". Benchmaxxing sells better.
Let's first start with y'all providing any proof that it was "benchmaxxing" that causes OEMs not to ship hardened allocators (and not - for example - breaking compatibility with users' software).
And then we can move the goalposts to "more secure distro with GrapheneOS" which isn't part of the conversation until you dragged it out.
Really? They're not using Scudo? The hardened_malloc used in GrapheneOS has a bunch of performance issues that were trade-offs against security. Every other major android distribution uses scudo as far as I know. Which OEMs are you thinking of?
Edit: Did some research after writing this? It appears that Samsung may be still using jemalloc, albeit a newer version than the one from the Android 11 days.
> 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?
Odd. Google Pixel 7 with GrapheneOS here. OsmAnd works perfectly fine for me without disabling any exploit protection options.
CoMaps behaves very very weirdly on GrapheneOS. Same with OrganicMaps.
Osmand and GMaps are working fine.
Waze is almost melting the poor thing. Beside of that working fine.
Waze works perfectly fine for me
Anyone writing about apps compatibility should specify if it's with or without the play services
Can you even run Waze/GMaps without Play services?
I use Comaps daily on GrapheneOS on a Pixel 8 Pro and it works great.
I wonder if a website using leaflet.js has better or worse performance in the said case. If it does better, then maybe the problem is on OsmAnd's side?
Huh. Yeah, it is noticeably faster on my 9a with that disabled. I wonder what they're doing differently...
https://news.ycombinator.com/item?id=45358216
Maybe the actual solution is to improve, replace the application.
Or maybe there's a reason why the mainline Android OEMs don't ship that allocator by default.
The fairly obvious answer here is "OEMs don't care about security because very few people will pay for it, either with $ or time". Benchmaxxing sells better.
That's trivially provable as false.
If so, I'd love to know which OEM you're thinking of who ships an Android distro more secure than GrapheneOS.
Let's first start with y'all providing any proof that it was "benchmaxxing" that causes OEMs not to ship hardened allocators (and not - for example - breaking compatibility with users' software).
And then we can move the goalposts to "more secure distro with GrapheneOS" which isn't part of the conversation until you dragged it out.
Because they cut costs on hardware and not all ship MTE enabled ARMs.
Maybe... legacy?
There needs to be a wall of shame for apps that abuse hardware owned by users
How's it abusing anything? It's an Android app that works fine with the default Android memory allocator.
The AOSP memory allocator is seldom the one used by OEMs.
Really? They're not using Scudo? The hardened_malloc used in GrapheneOS has a bunch of performance issues that were trade-offs against security. Every other major android distribution uses scudo as far as I know. Which OEMs are you thinking of?
Edit: Did some research after writing this? It appears that Samsung may be still using jemalloc, albeit a newer version than the one from the Android 11 days.
That doesn't necessarily mean it isn't being abusive, just that said allocator tolerates it okay.
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?
Seems unlikely, it's java so this is likely related to loading large amounts of objects and having the GC thrashing.
The core is C++ afaik.