or ----------------------------------------------------------------------------------------------------------------------------------------------------- DALVIK THREADS: "main" prio=5 tid=3 WAIT | group="main" sCount=1 dsCount=0 s=0 obj=0x40018e50 | sysTid=1210 nice=0 sched=0/0 handle=-1095230308 at java.lang.Object.wait(Native Method) - waiting on <0x18ab68> (a android.os.MessageQueue) at java.lang.Object.wait(Object.java:288) at android.os.MessageQueue.next(MessageQueue.java:148) at android.os.Looper.loop(Looper.java:110) at android.app.ActivityThread.main(ActivityThread.java:3948) at java.lang.reflect.Method.invokeNative(Native Method) at java.lang.reflect.Method.invoke(Method.java:521) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:782) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:540) at dalvik.system.NativeStart.main(Native Method)
"Binder Thread #3" prio=5 tid=15 NATIVE | group="main" sCount=1 dsCount=0 s=0 obj=0x4375aa50 | sysTid=1216 nice=0 sched=0/0 handle=1506232 at dalvik.system.NativeStart.run(Native Method) "Binder Thread #2" prio=5 tid=13 NATIVE | group="main" sCount=1 dsCount=0 s=0 obj=0x437567a0 | sysTid=1215 nice=0 sched=0/0 handle=1487784 at dalvik.system.NativeStart.run(Native Method) "Binder Thread #1" prio=5 tid=11 NATIVE | group="main" sCount=1 dsCount=0 s=0 obj=0x43754f90 | sysTid=1214 nice=0 sched=0/0 handle=1487280 at dalvik.system.NativeStart.run(Native Method) "JDWP" daemon prio=5 tid=9 VMWAIT | group="system" sCount=1 dsCount=0 s=0 obj=0x437542a0 | sysTid=1213 nice=0 sched=0/0 handle=1484704 at dalvik.system.NativeStart.run(Native Method) "Signal Catcher" daemon prio=5 tid=7 RUNNABLE | group="system" sCount=0 dsCount=0 s=0 obj=0x437541e8 | sysTid=1212 nice=0 sched=0/0 handle=1316760 at dalvik.system.NativeStart.run(Native Method) "HeapWorker" daemon prio=5 tid=5 VMWAIT | group="system" sCount=1 dsCount=0 s=0 obj=0x42998c30 | sysTid=1211 nice=0 sched=0/0 handle=1317480 at dalvik.system.NativeStart.run(Native Method) ----- end 1210 ----- ---------------------------------------------------------------------------------------------------------------------------------------------- On Wed, May 20, 2009 at 6:27 PM, Anonymous Anonymous < firewallbr...@googlemail.com> wrote: > How to analyze an ANR log !! :( > > something liek this? > > > --------------------------------------------------------------------------------------------------------------- > "pool-2-thread-1" prio=5 tid=25 WAIT > | group="main" sCount=1 dsCount=0 s=0 obj=0x437d1ea0 > | sysTid=1425 nice=0 sched=0/0 handle=2025912 > at java.lang.Object.wait(Native Method) > - waiting on <0x1b4830> (a java.lang.VMThread) > at java.lang.Thread.parkFor(Thread.java:1497) > at java.lang.LangAccessImpl.parkFor(LangAccessImpl.java:48) > at sun.misc.Unsafe.park(Unsafe.java:319) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:117) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1774) > at java.util.concurrent.DelayQueue.take(DelayQueue.java:120) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:503) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:496) > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:465 > > --------------------------------------------------------------------------------------------------------------------------------------------------- > > thanks > > > On Thu, Mar 19, 2009 at 8:27 AM, Dianne Hackborn <hack...@android.com>wrote: > >> The dialog is shown when an application isn't responding to the system, so >> the user can kill it without having to wait. It currently is shown in two >> main places: when the window manager waits to long on an event it has >> dispatched to an application, and when the activity manager waits too long >> on a serialized broadcast it has sent to an application (thus delaying any >> other recipients of the broadcast). >> >> On developer builds, you see the ANR dialog whenever either of these >> happens for any applications. On release builds, the dialog is only shown >> when the current foreground application is causing the ANR; background >> applications that are not responding to broadcasts are simply killed without >> the user being involved. >> >> The way you control this is by writing your code so it doesn't happen. :) >> >> On Wed, Mar 18, 2009 at 6:58 PM, Jag Dev <devj...@gmail.com> wrote: >> >>> Hello, >>> >>> What is the logic behind ANR popups? >>> >>> For example, >>> >>> When playing a music and doing random key presses results in this popup? >>> >>> The music app is trying to do something in the background? Even though >>> this popup is seen, the music app plays in the BG and hence if we select >>> "wait" then everything goes through fine. But this is kind off annoying or >>> giving a impression that something failed? >>> >>> Can you please let me know: >>> >>> 1. How do we control this popup and where is the control? >>> 2. What is the logic behind ANRs'? >>> >>> Thanks for your time and help. >>> Dev >>> >>> >>> >> >> >> -- >> Dianne Hackborn >> Android framework engineer >> hack...@android.com >> >> Note: please don't send private questions to me, as I don't have time to >> provide private support. All such questions should be posted on public >> forums, where I and others can see and answer them. >> >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-framework" group. To post to this group, send email to android-framework@googlegroups.com To unsubscribe from this group, send email to android-framework+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-framework?hl=en -~----------~----~----~----~------~----~------~--~---
