Consistent OutOfMemoryError Crashes

Graphxel

Recently installed GOS onto a new Pixel 9. Until yesterday I had no issues with stability. Yesterday I began installing many of the apps I had on my previous phone. Since then I've been getting pretty consistent OutOfMemoryError crashes when actively using my phone (every ₂₀-30 min), with performance slowing a lot before GOS finally crashses.

So I'm assuming it's one of these newly-installed apps that's the issue. I tried allowing Google Play Services to run consistently, but that didn't seem to help. So I'm not sure whether it's a permission issue with one of the apps or what.

Below is the system_server crash report for the most recent crash (I have the reports for the other crashes if needed). I also have the system log available to reference, but it's 66000 lines long, and I didn't see a way to attach files, so I'm not sure what the preferred method on the forums is for posting those.

Thanks in advance!

type: crash

SystemUptimeMs: 12130487
Process: system_server
Timestamp: 2025-12-07 10:24:22.010-0500
Build: google/tokay/tokay:16/BP3A.251105.015/2025120401: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 48 byte allocation with 5185184 free bytes and 5063KB until OOM, target footprint 536870912, growth limit 536870912; giving up on allocation because <1% of heap free after GC.
at java.nio.ByteBuffer.wrap(ByteBuffer.java:426)
at android.net.connectivity.com.android.net.module.util.ip.NetlinkMonitor.handlePacket(NetlinkMonitor.java:154)
at android.net.connectivity.com.android.net.module.util.ip.NetlinkMonitor.handlePacket(NetlinkMonitor.java:59)
at android.net.connectivity.com.android.net.module.util.FdEventsReader.handleInput(FdEventsReader.java:277)
at android.net.connectivity.com.android.net.module.util.FdEventsReader.lambda$createAndRegisterFd$0(FdEventsReader.java:233)
at android.net.connectivity.com.android.net.module.util.FdEventsReader.$r8$lambda$nOpviJ36K9yTVIlKPXopclWm250(FdEventsReader.java:0)
at android.net.connectivity.com.android.net.module.util.FdEventsReader$$ExternalSyntheticLambda0.onFileDescriptorEvents(R8$$SyntheticClass:0)
at android.os.MessageQueue.dispatchEvents(MessageQueue.java:647)
at android.os.MessageQueue.nativePollOnce(Native Method)
at android.os.MessageQueue.nextConcurrent(MessageQueue.java:923)
at android.os.MessageQueue.next(MessageQueue.java:1110)
at android.os.Looper.loopOnce(Looper.java:197)
at android.os.Looper.loop(Looper.java:349)
at android.os.HandlerThread.run(HandlerThread.java:100)

de0u

Graphxel Below is the system_server crash report for the most recent crash (I have the reports for the other crashes if needed).

That one crash doesn't make it clear what's going on, other than that the system is out of memory. Posting a few more might (or might not) shed light on the cause. Disabling apps one by one might converge on the problem faster.

Is the built-in GrapheneOS launcher being used, or some other launcher?

MetropleX

Graphxel Check the possible solution from this similar issue on the tracker and please feedback, happened to one user on stock so appears to be upstream.

https://github.com/GrapheneOS/os-issue-tracker/issues/5590

Graphxel

de0u Disabling apps one by one might converge on the problem faster.

Yeah I thought the same thing after posting. I've started going through and disabling the new apps to see if one stands out

de0u Is the built-in GrapheneOS launcher being used, or some other launcher?

I'm using Nova Launcher.

One of the things I tried was removing the Nova Launcher-created widget for my music app off the home screen, as I noticed there were lots of rapid bursts of system log entries for the widget. So far this seems like it may have been the case, but I need to sit down and actually mess around on my phone for a bit to "stress test" the memory usage.

Graphxel

MetropleX Thankfully this doesn't seem to be the same problem that I'm experiencing, as the time-to-crash is a lot longer for me, and seems to require active use of my phone. I also don't see the notifications the poster of that thread saw.

I'll keep that thread in mind though in case my issue starts snowballing for some reason.

MetropleX

Graphxel regards Nova are you on the latest version or the last Beta APK to be published to their website outside of Google Play?

Graphxel

MetropleX I installed it off of Google Play, didn't sideload it, so I presume the latest version

MetropleX

Graphxel Nova definitely has issues with music widgets, just added one, tapped an album which opened it in the app but everytime I do this then swipe home MTE crash is triggered. So it does indeed appear it has memory corruption bugs and issues.

Graphxel

MetropleX This was definitely the issue. It's been a few days since I took the widget for the music app off my home screen and I haven't had any crashes. Kind of a bummer that I can't have the widget, but I'll get over it.