Trying to find reliable steps to reproduce this ANR is proving very time-consuming. It would probably take dozens of hours for me to do so. If I knew how to automate hundreds of actions in succession on an Android device I might be able to determine somewhat reliable steps in a few hours. But I have no experience with that. I will likely just have to reproduce this just once more, while recording the behaviour using adb logcat
. Not sure that will be good enough for someone to debug the issue, but it's probably better than nothing.
Android 15 is right around the corner, so there's a possibility this might not be reproducible then. Would in any case require testing under stock PixelOS as well.
So far, the context around the ANR is this:
- Device has a moderate or high degree of uptime – at least several hours
- Several apps are open at once
- The user has actively been using many apps in a short time, and the apps are running when the ANR occurs
- One or more secondary profiles may be running simultaneously, although the ANR can also be triggered in the Owner profile without any profile running in the background
Under this context or a similar one, the user installs a system language which has not been installed in that specific profile before, and ANRs in several system apps are triggered. The ANRs do not stop, and the device has to be forced powered-off.
Given the context, it sounds like the device could be running out of available system resources, such as having a heavy CPU load, and then not being able to force-stop processes that causes heavy load – although that is an uneducated guess.