2011-06-23 180 views
1

我在運行我的應用程序時遇到了這些堆棧跟蹤,其中的崩潰。我知道它必須對「ANR keyDispatchingTimedOut」做些什麼。我是Android開發新手,我需要一些幫助來閱讀這些痕跡。需要幫助閱讀堆棧跟蹤

DALVIK THREADS: 
"main" prio=5 tid=1 NATIVE 
    | group="main" sCount=1 dsCount=0 s=N obj=0x40028ae0 self=0xcd58 
    | sysTid=7787 nice=0 sched=0/0 cgrp=default handle=-1345021904 
    | schedstat=(12266998315 6628478984 2116) 
    at android.database.sqlite.SQLiteQuery.native_fill_window(Native Method) 
    at android.database.sqlite.SQLiteQuery.fillWindow(SQLiteQuery.java:70) 
    at android.database.sqlite.SQLiteCursor.fillWindow(SQLiteCursor.java:299) 
    at android.database.sqlite.SQLiteCursor.getCount(SQLiteCursor.java:280) 
    at android.database.AbstractCursor.moveToPosition(AbstractCursor.java:171) 
    at android.database.AbstractCursor.moveToFirst(AbstractCursor.java:248) 
    at george.android.eortologioAlpha.EortologioAlpha.statheresPlhrhsGiortes(EortologioAlpha.java:171) 
    at george.android.eortologioAlpha.EortologioAlpha.giortazei(EortologioAlpha.java:265) 
    at george.android.eortologioAlpha.EortologioAlpha.eortazomenhEpafh(EortologioAlpha.java:281) 
    at george.android.eortologioAlpha.EortologioAlpha.onCreate(EortologioAlpha.java:474) 
    at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1065) 
    at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2745) 
    at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2797) 
    at android.app.ActivityThread.access$2300(ActivityThread.java:135) 
    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2132) 
    at android.os.Handler.dispatchMessage(Handler.java:99) 
    at android.os.Looper.loop(Looper.java:143) 
    at android.app.ActivityThread.main(ActivityThread.java:4914) 
    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:858) 
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616) 
    at dalvik.system.NativeStart.main(Native Method) 

"Binder Thread #2" prio=5 tid=5 NATIVE 
    | group="main" sCount=1 dsCount=0 s=N obj=0x447cdb78 self=0x130b40 
    | sysTid=7791 nice=0 sched=0/0 cgrp=default handle=1248000 
    | schedstat=(6164551 6774901 9) 
    at dalvik.system.NativeStart.run(Native Method) 

"Binder Thread #1" prio=5 tid=4 NATIVE 
    | group="main" sCount=1 dsCount=0 s=N obj=0x447c9b18 self=0x139258 
    | sysTid=7790 nice=0 sched=0/0 cgrp=default handle=1271880 
    | schedstat=(12756347 35614013 13) 
    at dalvik.system.NativeStart.run(Native Method) 

"Signal Catcher" daemon prio=5 tid=3 RUNNABLE 
    | group="system" sCount=0 dsCount=0 s=N obj=0x447c81e8 self=0x136948 
    | sysTid=7789 nice=0 sched=0/0 cgrp=default handle=1249544 
    | schedstat=(4150389 20233155 9) 
    at dalvik.system.NativeStart.run(Native Method) 

"HeapWorker" daemon prio=5 tid=2 VMWAIT 
    | group="system" sCount=1 dsCount=0 s=N obj=0x43a1c590 self=0x136708 
    | sysTid=7788 nice=0 sched=0/0 cgrp=default handle=1248984 
    | schedstat=(247253419 294708251 77) 
    at dalvik.system.NativeStart.run(Native Method) 
+0

可能重複[Android的 - 我怎麼調查的ANR(http://stackoverflow.com/questions/704311/android-how-do-i-investigate-an-anr) –

回答

2

ANR keyDispatchingTimedOut意味着你的活動被卡住了什麼事情而無法到下一個用戶輸入做出反應。

要閱讀堆棧跟蹤,只需掃描它直到看到包名稱,這就是您要專注的位。

我以前曾經回答了這個:ANR keyDispatchingTimedOut error

ANR錯誤

活動沒有響應。

您的活動需要很長時間才能對Android操作系統說'嘿,我還活着'! (這是UI線程所做的)。

http://developer.android.com/guide/practices/design/responsiveness.html

基本上如果你讓UI線程做一些複雜的任務,它太忙着做你的任務是告訴操作系統,它仍然是「活着」。

http://developer.android.com/resources/articles/painless-threading.html

你應該將你的數據庫中選擇/更新/刪除代碼到另一個線程,然後使用一個回調來告訴你已經完成了UI線程和做的結果的東西。

http://developer.android.com/resources/articles/timed-ui-updates.html