A GrapheneOS user experienced significant slowdowns with the OpenstreetMap for Android (Osmand) application on a Pixel 8 device. This performance degradation was not observed on other Android devices, leading to an investigation into the cause specific to GrapheneOS.
The performance issue was traced to GrapheneOS's hardened memory allocator. This security feature, while beneficial for overall system security, introduced considerable overhead for Osmand, likely due to the app's continuous data loading and discarding during map scrolling.
A solution was found by disabling the hardened memory allocator specifically for the Osmand app. This setting is accessible by long-tapping the app icon, selecting 'info', and navigating to 'Exploit protection'. After disabling the 'hardened memory allocator' option and restarting Osmand, the app's performance returned to normal.
Disabling the hardened memory allocator carries a security drawback. However, for Osmand, which primarily handles offline map data and infrequent online updates, the user determined that the trade-off between security and performance was acceptable in this specific context.
✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →
One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.
One email a day. Unsubscribe in one click, any time.
Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.
▶ Play today's briefNew every morning, and the back catalogue is archived by date.
A GrapheneOS user identified that the hardened memory allocator caused performance issues for the Osmand app. Disabling this protection on a per-app basis resolved the slowdown, allowing Osmand to run at normal speeds.