os-issue-tracker
os-issue-tracker copied to clipboard
GrapheneOS
GrapheneOS lagging then crashing
type: crash
SystemUptimeMs: 89599855
Process: system_server
Build: google/oriole/oriole:14/AP2A.240605.024/2024062000:user/release-keys
Crash-Handler: com.android.internal.os.RuntimeInit$KillApplicationHandler
Loading-Progress: 1.0
Dropped-Count: 0
java.lang.OutOfMemoryError: Failed to allocate a 24 byte allocation with 5116320 free bytes and 4996KB until OOM, target footprint 536870912, growth limit 536870912; giving up on allocation because <1% of heap free after GC.
at android.net.connectivity.com.android.server.connectivity.NetworkRanker.mightBeat(NetworkRanker.java:386)
at android.net.connectivity.com.android.server.ConnectivityService.informOffer(ConnectivityService.java:10647)
at android.net.connectivity.com.android.server.ConnectivityService.issueNetworkNeeds(ConnectivityService.java:10582)
at android.net.connectivity.com.android.server.ConnectivityService.issueNetworkNeeds(ConnectivityService.java:10575)
at android.net.connectivity.com.android.server.ConnectivityService.rematchNetworksAndRequests(ConnectivityService.java:10335)
at android.net.connectivity.com.android.server.ConnectivityService.rematchAllNetworksAndRequests(ConnectivityService.java:10319)
at android.net.connectivity.com.android.server.ConnectivityService.handleRegisterNetworkRequests(ConnectivityService.java:5456)
at android.net.connectivity.com.android.server.ConnectivityService.handleRegisterNetworkRequest(ConnectivityService.java:5421)
at android.net.connectivity.com.android.server.ConnectivityService.-$$Nest$mhandleRegisterNetworkRequest(ConnectivityService.java:0)
at android.net.connectivity.com.android.server.ConnectivityService$InternalHandler.handleMessage(ConnectivityService.java:6339)
at android.os.Handler.dispatchMessage(Handler.java:107)
at android.os.Looper.loopOnce(Looper.java:232)
at android.os.Looper.loop(Looper.java:317)
at android.os.HandlerThread.run(HandlerThread.java:85)
This happens like once every second day.
We'll need more info about how this is being triggered to do something about it. You appear to be triggering a memory leak in system_server, likely due to an upstream bug.
