type: crash
flags: dev options enabled
SystemUptimeMs: 43403095
Process: system_server
Timestamp: 2024-11-20 15:50:59.915+0100
Build: google/bluejay/bluejay:15/AP3A.241105.007/2024110700:user/release-keys
Crash-Handler: com.android.internal.os.RuntimeInit$KillApplicationHandler
Loading-Progress: 1.0
Dropped-Count: 0
java.util.concurrent.TimeoutException: android.window.WindowContext.finalize() timed out after 10 seconds
at com.android.server.wm.WindowManagerService.detachWindowContext(WindowManagerService.java:3068)
at android.window.WindowTokenClientController.detachIfNeeded(WindowTokenClientController.java:178)
at android.window.WindowContextController.detachIfNeeded(WindowContextController.java:153)
at android.window.WindowContext.release(WindowContext.java:114)
at android.window.WindowContext.finalize(WindowContext.java:107)
at java.lang.Daemons$FinalizerDaemon.doFinalize(Daemons.java:370)
at java.lang.Daemons$FinalizerDaemon.processReference(Daemons.java:350)
at java.lang.Daemons$FinalizerDaemon.runInternal(Daemons.java:322)
at java.lang.Daemons$Daemon.run(Daemons.java:131)
at java.lang.Thread.run(Thread.java:1012)
Crashes with disabled dev options too.
further interesting observations:
i wanted to switch from my work profile to a secondary profile. i was immediately logged in without having to enter the pin. so the old session was still cached somewhere and that after several days and restarts of the phone.
when i tried to go back to the main profile, the system crashed and restarted again. after the restart, i tried to go back to the secondary profile, but the system crashed immediately. the secondary profile was no longer accessible!!
luckily i found the option “run in background” in the user settings that you can set per profile. after another restart the secondary profile was accessible again.
i think this bug needs to be fixed. other people may not be so lucky. i also find it problematic that a login session (2nd profile) survives sys crashes and system restarts.