Fixed
Status Update
No update yet.
Comments
uc...@google.com
rp...@google.com
I just attached a minimal test application with duplicated and multiline traces. Provided are a couple of logcat files and screenshots.
To me this isn'r really a big problem, since AS compiles my application and lets me debug it. That's what I use it for in my company. I just found it a bit annoying that something that worked one way in AS 2.x and 3.0, suddenly changed in 3.1. The new way results more time-consuming to me while debugging and reviewing the logs.
Could this be made configurable? Not necessarily in the UI, but editing some properties file. Thanks. :)
To me this isn'r really a big problem, since AS compiles my application and lets me debug it. That's what I use it for in my company. I just found it a bit annoying that something that worked one way in AS 2.x and 3.0, suddenly changed in 3.1. The new way results more time-consuming to me while debugging and reviewing the logs.
Could this be made configurable? Not necessarily in the UI, but editing some properties file. Thanks. :)
du...@google.com
I have the same problem.
sa...@gmail.com
I also have the same problem.
du...@google.com
I also have the same problem.
Description
Attach a device while android studio is running. Watch logcat. Observer this over and over again:
07-24 11:59:39.434 W/MessageQueue( 8492): Handler (android.os.Handler) {506b8aa} sending message to a Handler on a dead thread
07-24 11:59:39.434 W/MessageQueue( 8492): java.lang.IllegalStateException: Handler (android.os.Handler) {506b8aa} sending message to a Handler on a dead thread
07-24 11:59:39.434 W/MessageQueue( 8492): at android.os.MessageQueue.enqueueMessage(MessageQueue.java:545)
07-24 11:59:39.434 W/MessageQueue( 8492): at android.os.Handler.enqueueMessage(Handler.java:662)
07-24 11:59:39.434 W/MessageQueue( 8492): at android.os.Handler.sendMessageAtTime(Handler.java:631)
07-24 11:59:39.434 W/MessageQueue( 8492): at android.os.Handler.sendMessageDelayed(Handler.java:601)
07-24 11:59:39.434 W/MessageQueue( 8492): at
07-24 11:59:39.434 W/MessageQueue( 8492): at android.os.ResultReceiver$MyResultReceiver.send(ResultReceiver.java:57)
07-24 11:59:39.434 W/MessageQueue( 8492): at com.android.internal.os.IResultReceiver$Stub.onTransact(IResultReceiver.java:58)
07-24 11:59:39.434 W/MessageQueue( 8492): at android.os.Binder.execTransact(Binder.java:697)
07-24 11:59:39.755 D/AndroidRuntime( 8503): >>>>>> START com.android.internal.os.RuntimeInit uid 0 <<<<<<
07-24 11:59:39.866 I/app_process( 8503): The ClassLoaderContext is a special shared library.
07-24 11:59:39.908 D/AndroidRuntime( 8503): Calling main entry
07-24 11:59:39.930 I/app_process( 8503): System.exit called, status: 0
07-24 11:59:39.931 I/AndroidRuntime( 8503): VM exiting with result code 0.
07-24 11:59:39.931 W/MessageQueue( 8503): Handler (android.os.Handler) {506b8aa} sending message to a Handler on a dead thread
07-24 11:59:39.931 W/MessageQueue( 8503): java.lang.IllegalStateException: Handler (android.os.Handler) {506b8aa} sending message to a Handler on a dead thread
07-24 11:59:39.931 W/MessageQueue( 8503): at android.os.MessageQueue.enqueueMessage(MessageQueue.java:545)
07-24 11:59:39.931 W/MessageQueue( 8503): at android.os.Handler.enqueueMessage(Handler.java:662)
07-24 11:59:39.931 W/MessageQueue( 8503): at android.os.Handler.sendMessageAtTime(Handler.java:631)
07-24 11:59:39.931 W/MessageQueue( 8503): at android.os.Handler.sendMessageDelayed(Handler.java:601)
07-24 11:59:39.931 W/MessageQueue( 8503): at
07-24 11:59:39.931 W/MessageQueue( 8503): at android.os.ResultReceiver$MyResultReceiver.send(ResultReceiver.java:57)
07-24 11:59:39.931 W/MessageQueue( 8503): at com.android.internal.os.IResultReceiver$Stub.onTransact(IResultReceiver.java:58)
07-24 11:59:39.931 W/MessageQueue( 8503): at android.os.Binder.execTransact(Binder.java:697)
07-24 11:59:40.323 D/AndroidRuntime( 8518): >>>>>> START com.android.internal.os.RuntimeInit uid 0 <<<<<<
07-24 11:59:40.433 I/app_process( 8518): The ClassLoaderContext is a special shared library.
07-24 11:59:40.475 D/AndroidRuntime( 8518): Calling main entry
07-24 11:59:40.493 I/app_process( 8518): System.exit called, status: 0
07-24 11:59:40.494 I/AndroidRuntime( 8518): VM exiting with result code 0.
07-24 11:59:40.502 W/MessageQueue( 8518): Handler (android.os.Handler) {7a95313} sending message to a Handler on a dead thread
07-24 11:59:40.502 W/MessageQueue( 8518): java.lang.IllegalStateException: Handler (android.os.Handler) {7a95313} sending message to a Handler on a dead thread
07-24 11:59:40.502 W/MessageQueue( 8518): at android.os.MessageQueue.enqueueMessage(MessageQueue.java:545)
07-24 11:59:40.502 W/MessageQueue( 8518): at android.os.Handler.enqueueMessage(Handler.java:662)
07-24 11:59:40.502 W/MessageQueue( 8518): at android.os.Handler.sendMessageAtTime(Handler.java:631)
07-24 11:59:40.502 W/MessageQueue( 8518): at android.os.Handler.sendMessageDelayed(Handler.java:601)
07-24 11:59:40.502 W/MessageQueue( 8518): at
07-24 11:59:40.502 W/MessageQueue( 8518): at android.os.ResultReceiver$MyResultReceiver.send(ResultReceiver.java:57)
07-24 11:59:40.502 W/MessageQueue( 8518): at com.android.internal.os.IResultReceiver$Stub.onTransact(IResultReceiver.java:58)
07-24 11:59:40.502 W/MessageQueue( 8518): at android.os.Binder.execTransact(Binder.java:697)
It seems android studio is executing commands on my device in a loop and generating all this noise.
Commands based on running PS appear to be:
17254 root 9632 S /system/bin/sh -c stat -c %u /proc/6336 | xargs -n 1 pm list packages --uid
17257 root 11296 S xargs -n 1 pm list packages --uid
17268 root 9632 S /system/bin/sh -
17275 root 3976m S {main} app_process /system/bin
It seems to be looking for associated applications by uid or something? Please make this quieter, it's very annoying to see all this junk coming out of logcat. This did not used to happen with older versions Android Studio.