[Galaxy Note 3 Android Development] ronjwright:
I wanted to post a follow-up on the second bug that I reported with the launcher shutting down while the mobile connection is lost, which is still occurring in build 7.9. I noticed that whenever the launcher shuts down, I saw messages in the logcat similar to the following, which should have been my first suspicion:

02-25 04:57:13.944 W/WindowManager( 9393): Window freeze timeout expired.
02-25 04:57:13.944 W/WindowManager( 9393): Force clearing orientation change: Window{2de19dc1 u0 NavigationBar}
02-25 04:57:13.944 W/WindowManager( 9393): Force clearing orientation change: Window{1982bc83 u0 StatusBar}
02-25 04:57:13.944 W/WindowManager( 9393): Force clearing orientation change: Window{326500c u0 com.android.systemui.ImageWallpaper}
02-25 04:57:15.406 I/WindowManager( 9393): Screen frozen for +3s500ms due to Window{18b005ab u0 com.google.android.googlequicksearchbox/com.google.android.launcher.GEL}

02-25 05:01:05.646 W/WindowManager( 9393): Window freeze timeout expired.
02-25 05:01:05.646 W/WindowManager( 9393): Force clearing orientation change: Window{2de19dc1 u0 NavigationBar}
02-25 05:01:05.646 W/WindowManager( 9393): Force clearing orientation change: Window{1982bc83 u0 StatusBar}
02-25 05:01:05.646 W/WindowManager( 9393): Force clearing orientation change: Window{2e7a4238 u0 com.google.android.googlequicksearchbox/com.google.android.launcher.GEL}
02-25 05:01:05.646 W/WindowManager( 9393): Force clearing orientation change: Window{326500c u0 com.android.systemui.ImageWallpaper}
02-25 05:01:05.786 I/WindowManager( 9393): Screen frozen for +2s213ms due to AppWindowToken{31af07c5 token=Token{1c30d82f ActivityRecord{1e27160e u0 com.google.android.googlequicksearchbox/com.google.android.launcher.GEL t77}}}

I studied the behavior of the launcher shutdowns over a longer period of time and looked harder at the logcat, and I now have doubt that the libc segfaults have anything to do with this. I saw a correlation between the timestamps of the window manager messages and the times at which I observe the shutdowns, but could not see any correlation between the timestamps of the libc segfault messages and the times at which I observe the shutdowns. In addition, while the mobile connection is lost, I noticed that some process might be leaking file descriptors, as shown in the following logcat output:

W/System.err( 9916): java.io.IOException: Error running exec(). Command: [am, broadcast, -a, android.intent.action.LTE_SMS_STATUS, --ei, ltesms, 3] Working Directory: null Environment: null
W/System.err( 9916):	at java.lang.ProcessManager.exec(ProcessManager.java:211)
W/System.err( 9916):	at java.lang.Runtime.exec(Runtime.java:173)
W/System.err( 9916):	at java.lang.Runtime.exec(Runtime.java:246)
W/System.err( 9916):	at java.lang.Runtime.exec(Runtime.java:189)
W/System.err( 9916):	at com.android.internal.telephony.hlteRIL.processUnsolicited(hlteRIL.java:265)
W/System.err( 9916):	at com.android.internal.telephony.RIL.processResponse(RIL.java:2607)
W/System.err( 9916):	at com.android.internal.telephony.RIL$RILReceiver.run(RIL.java:602)
W/System.err( 9916):	at java.lang.Thread.run(Thread.java:818)
W/System.err( 9916): Caused by: java.io.IOException: Too many open files
W/System.err( 9916):	at java.lang.ProcessManager.exec(Native Method)
W/System.err( 9916):	at java.lang.ProcessManager.exec(ProcessManager.java:209)
W/System.err( 9916):	... 7 more

This exception backtrace is printed out repeatedly in batches until a mobile connection is re-established. I sort of recall seeing the logcat outputs for the window manager freezes and the possible file descriptor leak similar to what is shown here in build 7.7, but I wasn't sure whether these logcat outputs were potentially relevant to the launcher problem until now.