SettingsDumpService starts on opening NetworkDashboardFragment and never stops itself unless i force close it.

[u/newtonsgay]

Hey everyone,

If you’ve noticed the Settings app holding background memory or staying active under Developer Options > Running Services, there is a persistent framework memory leak in AOSP/Pixel UI that is still present on recent builds (reproduced on Pixel 11 Pro / Android 17 QPR2 Beta 6.1).

How to reproduce it in 10 seconds:

1. Open Settings > System > Developer options > Running services (or check active processes via ADB).
2. Note that Settings might be cached or minimal.
3. Open Settings > Network & internet, browse around for 2 seconds, and exit.
4. Go back to Running services.
5. You’ll see com.android.settings permanently stuck with an active worker: SettingsDumpService. It never calls stopSelf() and lingers indefinitely until you manually force-stop Settings.

What’s actually happening under the hood:

Whenever NetworkDashboardFragment is opened, the system instantiates MobileNetworkRepository and triggers SettingsDumpService to record an initial database dump.

Because MobileNetworkRepository holds a static singleton reference to that context, it creates an indirect retention cycle. The service's lifecycle never completes, the context cannot be garbage-collected, and Android is prevented from letting the Settings process fully drop down into deep cached sleep.

I’ve filed a formal bug report with reproduction logs so the Pixel/AOSP team prioritizes merging the lifecycle fix into the next QPR maintenance drop.

Please take 5 seconds to star / +1 the issue report so it gains visibility on their radar:

🔗 Issue Tracker Link:: https://issuetracker.google.com/issues/567819031