GrapheneOS – When an app is slow

You can speed up specific GrapheneOS apps by disabling their hardened memory allocator, with a minor security trade-off.

A GrapheneOS user discovered that the OpenStreetMap (Osmand) app ran significantly slower on their Pixel 8 device due to the operating system's hardened memory allocator. This feature, designed to enhance security by adding overhead, caused performance issues for Osmand, which frequently loads and discards map data. The user found that disabling the hardened memory allocator on a per-app basis restored Osmand's speed to previous levels. While this introduces a minor security trade-off, the user deemed it acceptable for Osmand as it primarily fetches map data offline and only occasionally updates from the internet. The process involves navigating to the app's info screen, selecting 'Exploit protection,' and toggling off the 'hardened memory allocator.' Another user noted a similar battery drain and performance issue with Waze on GrapheneOS, suggesting the same fix might apply.

The GrapheneOS hardened memory allocator, while a strong security feature, presents a performance bottleneck for certain applications like Osmand that rely on rapid data loading and unloading. This discovery highlights a common tension in mobile security: the trade-off between robust protection and user experience, particularly for apps with demanding I/O operations. The ability to selectively disable these protections on a per-app basis offers a pragmatic solution for users prioritizing speed in specific use cases, though it necessitates an individual risk assessment.

This per-app exploit protection toggle demonstrates GrapheneOS's granular control over security features, allowing users to tailor their device's security posture to their specific app usage and threat model. It suggests that other applications with similar performance sensitivities might also benefit from this adjustment, opening the door for improved usability without a complete abandonment of GrapheneOS's security framework. Users will need to weigh the benefits of performance gains against the reduced exploit mitigation for each app they modify.