GrapheneOS – When an app is slow

negative_zero•about 2 hours ago

Odd. Google Pixel 7 with GrapheneOS here. OsmAnd works perfectly fine for me without disabling any exploit protection options.

hadi77ir•about 1 hour ago

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?

Groxx•about 2 hours ago

Huh. Yeah, it is noticeably faster on my 9a with that disabled. I wonder what they're doing differently...

pjmlp•about 3 hours ago

Maybe the actual solution is to improve, replace the application.

izacus•about 3 hours ago

Or maybe there's a reason why the mainline Android OEMs don't ship that allocator by default.

Groxx•about 2 hours ago

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.

pjmlp•about 2 hours ago

Because they cut costs on hardware and not all ship MTE enabled ARMs.

mohamedkoubaa•about 3 hours ago

There needs to be a wall of shame for apps that abuse hardware owned by users

yjftsjthsd-h•about 2 hours ago

How's it abusing anything? It's an Android app that works fine with the default Android memory allocator.

pjmlp•about 2 hours ago

The AOSP memory allocator is seldom the one used by OEMs.

perching_aix•about 2 hours ago

That doesn't necessarily mean it isn't being abusive, just that said allocator tolerates it okay.

perching_aix•about 3 hours ago

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•about 3 hours ago

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

GrapheneOS – When an app is slow

⚡ Community Insights

Discussion (25 Comments)Read Original on HackerNews