編輯:關於Android編程
當發生ANR後,首先需要查看log信息以及trace文件(系統都會在/data/anr/目錄下生成trace文件)分析出ANR原因。通過以下分析並不能解決所有碰到的ANR,但程序自身原因導致的ANR問題基本都能找到原因。
I/InputDispatcher( 220): Application is not responding:Window{2b263310com.android.email/com.android.email.activity.SplitScreenActivitypaused=false}. 5009.8ms since event, 5009.5ms since waitstarted --ANR時所處的界面 I/WindowManager( 220): Input event dispatching timedout sendingtocom.android.email/com.android.email.activity.SplitScreenActivity --可看出ANR的類型 (KeyDispatchTimeout(5 seconds)、BroadcastTimeout(10 seconds)、ServiceTimeout(20 seconds) ) I/Process( 220): Sending signal. PID: 21404 SIG: 3---生成trace.txt的時間 I/dalvikvm(21404):threadid=4: reacting to signal 3 …… E/ActivityManager( 220): ANR in com.android.email(com.android.email/.activity.SplitScreenActivity) E/ActivityManager( 220): Reason:keyDispatchingTimedOut E/ActivityManager( 220): Load: 8.68 / 8.37 / 8.53 E/ActivityManager( 220):CPUusage from 4361ms to 699ms ago----CPU在ANR發生前的使用情況 E/ActivityManager( 220): 5.5!404/com.android.email: 1.3% user + 4.1% kernel / faults: 10 minor E/ActivityManager( 220): 4.3"0/system_server: 2.7% user + 1.5% kernel / faults: 11 minor 2 major E/ActivityManager( 220): 0.9R/spi_qsd.0: 0% user + 0.9% kernel E/ActivityManager( 220): 0.5e/irq/170-cyttsp-: 0% user + 0.5% kernel E/ActivityManager( 220): 0.5)6/com.android.systemui: 0.5% user + 0% kernel E/ActivityManager( 220): 100%TOTAL: 4.8% user + 7.6% kernel + 87% iowait E/ActivityManager( 220):CPUusage from 3697ms to 4223ms later:-- ANR後CPU的使用量 E/ActivityManager( 220): 25!404/com.android.email: 25% user + 0% kernel / faults: 191 minor E/ActivityManager( 220): 16% 21603/__eas(par.hakan: 16% user + 0% kernel E/ActivityManager( 220): 7.2% 21406/GC: 7.2% user + 0% kernel E/ActivityManager( 220): 1.8% 21409/Compiler: 1.8% user + 0% kernel E/ActivityManager( 220): 5.5"0/system_server: 0% user + 5.5% kernel / faults: 1 minor E/ActivityManager( 220): 5.5% 263/InputDispatcher: 0% user + 5.5% kernel E/ActivityManager( 220): 32%TOTAL: 28% user + 3.7% kernel
從LOG可以看出ANR的類型,CPU的使用情況,如果CPU使用量接近100%,說明當前設備很忙,有可能是CPU饑餓導致了ANR
如果CPU使用量很少,說明主線程被BLOCK了
如果IOwait很高,說明ANR有可能是主線程在進行I/O操作造成的
除了看LOG,解決ANR還得需要trace.txt文件,
trace文件分析
pid 21404 at 2011-04-0113:12:14 ----- Cmdline: com.android.email DALVIK THREADS: (mutexes: tll=0tsl=0 tscl=0 ghl=0 hwl=0 hwll=0) "main" prio=5 tid=1NATIVE --表示線程狀態 ( /?dalvik/?vm/?Thread.h 0042 enum ThreadStatus { 0043 THREAD_UNDEFINED = -1, /* makes enum compatible with int32_t */ 0045 /* these match up with JDWP values */ 0046 THREAD_ZOMBIE = 0, /* TERMINATED */ 0047 THREAD_RUNNING = 1, /* RUNNABLE or running now */ 0048 THREAD_TIMED_WAIT = 2, /* TIMED_WAITING in Object.wait() */ 0049 THREAD_MONITOR = 3, /* BLOCKED on a monitor */ 0050 THREAD_WAIT = 4, /* WAITING in Object.wait() */ 0051 /* non-JDWP states */ 0052 THREAD_INITIALIZING = 5, /* allocated, not yet running */ 0053 THREAD_STARTING = 6, /* started, not yet on thread list */ 0054 THREAD_NATIVE = 7, /* off in a JNI native method */ 0055 THREAD_VMWAIT = 8, /* waiting on a VM resource */ 0056 THREAD_SUSPENDED = 9, /* suspended, usually by GC or debugger */ 0057 }; ) | group="main" sCount=1 dsCount=0obj=0x2aad2248 self=0xcf70 | sysTid=21404 nice=0 sched=0/0cgrp=[fopen-error:2] handle=1876218976 atandroid.os.MessageQueue.nativePollOnce(Native Method) atandroid.os.MessageQueue.next(MessageQueue.java:119) atandroid.os.Looper.loop(Looper.java:110) at android.app.ActivityThread.main(ActivityThread.java:3688) at java.lang.reflect.Method.invokeNative(Native Method) atjava.lang.reflect.Method.invoke(Method.java:507) atcom.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:866) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:624) at dalvik.system.NativeStart.main(Native Method)
說明主線程在等待下條消息進入消息隊列
我們可以很清楚的 解析 trace文件中 thread信息的含義了:
1. 第一行是 固定的頭, 指明下面的都是 當前運行的 dvm thread :“DALVIK THREADS:”
2. 第二行輸出的是該 進程裡各種線程互斥量的值。(具體的互斥量的作用在 dalvik 線程一章 單獨陳述)
3. 第三行輸出分別是 線程的名字(“main”),線程優先級(“prio=5”),線程id(“tid=1”) 以及線程的 類型(“NATIVE”)
案例1:關鍵詞:ContentResolver in AsyncTask onPostExecute, high iowait
Process:com.android.email Activity:com.android.email/.activity.MessageView Subject:keyDispatchingTimedOut CPU usage from 2550ms to -2814ms ago: 57/system_server: 3.5% user + 1.4% kernel / faults: 86 minor 20major 4.4% 1134/com.android.email: 0.7% user + 3.7% kernel /faults: 38 minor 19 major 4% 372/com.android.eventstream: 0.7%user + 3.3% kernel / faults: 6 minor 1.1% 272/com.android.phone:0.9% user + 0.1% kernel / faults: 33 minor 0.9%2/com.android.systemui: 0.9% user + 0% kernel 0@9/com.android.eventstream.telephonyplugin: 0% user + 0% kernel /faults: 2 minor 0.1% 632/com.android.devicemonitor: 0.1% user + 0%kernel 100%TOTAL: 6.9% user + 8.2% kernel +84%iowait pid 1134 at 2010-12-17 17:46:51 ----- Cmd line:com.android.email DALVIK THREADS: (mutexes: tll=0 tsl=0tscl=0 ghl=0 hwl=0 hwll=0) "main" prio=5 tid=1 WAIT |group="main" sCount=1 dsCount=0 obj=0x2aaca180self=0xcf20 | sysTid=1134 nice=0 sched=0/0 cgrp=[fopen-error:2]handle=1876218976 at java.lang.Object.wait(Native Method) -waiting on <0x2aaca218> (a java.lang.VMThread) atjava.lang.Thread.parkFor(Thread.java:1424) atjava.lang.LangAccessImpl.parkFor(LangAccessImpl.java:48) atsun.misc.Unsafe.park(Unsafe.java:337) atjava.util.concurrent.locks.LockSupport.park(LockSupport.java:157) atjava.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:808) atjava.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:841) atjava.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1171) atjava.util.concurrent.locks.ReentrantLock$FairSync.lock(ReentrantLock.java:200) atjava.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:261) atandroid.database.sqlite.SQLiteDatabase.lock(SQLiteDatabase.java:378) atandroid.database.sqlite.SQLiteCursor.(SQLiteCursor.java:222) atandroid.database.sqlite.SQLiteDirectCursorDriver.query(SQLiteDirectCursorDriver.java:53) atandroid.database.sqlite.SQLiteDatabase.rawQueryWithFactory(SQLiteDatabase.java:1356) atandroid.database.sqlite.SQLiteDatabase.queryWithFactory(SQLiteDatabase.java:1235) atandroid.database.sqlite.SQLiteDatabase.query(SQLiteDatabase.java:1189) atandroid.database.sqlite.SQLiteDatabase.query(SQLiteDatabase.java:1271) atcom.android.email.provider.EmailProvider.query(EmailProvider.java:1098) atandroid.content.ContentProvider$Transport.query(ContentProvider.java:187) atandroid.content.ContentResolver.query(ContentResolver.java:268) atcom.android.email.provider.EmailContent$Message.restoreMessageWithId(EmailContent.java:648) atcom.android.email.Controller.setMessageRead(Controller.java:658) atcom.android.email.activity.MessageView.onMarkAsRead(MessageView.java:700) atcom.android.email.activity.MessageView.access$2500(MessageView.java:98) atcom.android.email.activity.MessageView$LoadBodyTask.onPostExecute(MessageView.java:1290) atcom.android.email.activity.MessageView$LoadBodyTask.onPostExecute(MessageView.java:1255) atandroid.os.AsyncTask.finish(AsyncTask.java:417) atandroid.os.AsyncTask.access$300(AsyncTask.java:127) atandroid.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:429) atandroid.os.Handler.dispatchMessage(Handler.java:99) atandroid.os.Looper.loop(Looper.java:123) atandroid.app.ActivityThread.main(ActivityThread.java:3652) atjava.lang.reflect.Method.invokeNative(Native Method) atjava.lang.reflect.Method.invoke(Method.java:507) atcom.android.internal.os.ZygoteIn
原因:IOWait很高,說明當前系統在忙於I/O,因此數據庫操作被阻塞
案例2:關鍵詞:在UI線程進行網絡數據的讀寫
ANRin process: com.android.mediascape:PhotoViewer (last incom.android.mediascape:PhotoViewer) Annotation:keyDispatchingTimedOut CPU usage: Load: 6.74 / 6.89 / 6.12 CPUusage from 8254ms to 3224ms ago: ovider.webmedia: 4% = 4% user +0% kernel / faults: 68 minor system_server: 2% = 1% user + 0%kernel / faults: 18 minor re-initialized>: 0% = 0% user + 0%kernel / faults: 50 minor events/0: 0% = 0% user + 0%kernel TOTAL:7% = 6% user + 1% kernel DALVIKTHREADS: ""main"" prio=5 tid=3 NATIVE |group=""main"" sCount=1 dsCount=0 s=Yobj=0x4001b240 self=0xbda8 | sysTid=2579 nice=0 sched=0/0cgrp=unknown handle=-1343993184 atorg.apache.harmony.luni.platform.OSNetworkSystem.receiveStreamImpl(NativeMethod) atorg.apache.harmony.luni.platform.OSNetworkSystem.receiveStream(OSNetworkSystem.java:478) atorg.apache.harmony.luni.net.PlainSocketImpl.read(PlainSocketImpl.java:565) atorg.apache.harmony.luni.net.SocketInputStream.read(SocketInputStream.java:87) atorg.apache.harmony.luni.internal.net.www.protocol.http.HttpURLConnection$LimitedInputStream.read(HttpURLConnection.java:303) atjava.io.InputStream.read(InputStream.java:133) atjava.io.BufferedInputStream.fillbuf(BufferedInputStream.java:157) atjava.io.BufferedInputStream.read(BufferedInputStream.java:346) atandroid.graphics.BitmapFactory.nativeDecodeStream(Native Method) atandroid.graphics.BitmapFactory.decodeStream(BitmapFactory.java:459) atcom.android.mediascape.activity.PhotoViewerActivity.getPreviewImage(PhotoViewerActivity.java:4465) atcom.android.mediascape.activity.PhotoViewerActivity.dispPreview(PhotoViewerActivity.java:4406) atcom.android.mediascape.activity.PhotoViewerActivity.access$6500(PhotoViewerActivity.java:125) atcom.android.mediascape.activity.PhotoViewerActivity$33$1.run(PhotoViewerActivity.java:4558) atandroid.os.Handler.handleCallback(Handler.java:587) atandroid.os.Handler.dispatchMessage(Handler.java:92) atandroid.os.Looper.loop(Looper.java:123) atandroid.app.ActivityThread.main(ActivityThread.java:4370) atjava.lang.reflect.Method.invokeNative(Native Method) atjava.lang.reflect.Method.invoke(Method.java:521) atcom.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868) atcom.android.internal.os.ZygoteInit.main(ZygoteInit.java:626) atdalvik.system.NativeStart.main(Native Method)
關於網絡連接,在設計的時候可以設置個timeout的時間或者放入獨立的線程來處理。
關於Handler的問題,可以參考: http://developer.android.com/reference/android/os/Handler.html
案例3:Memoryleak/Thread leak
I/ActivityManager( 1190): ANR in process:android.process.acore (last in android.process.acore) I/ActivityManager( 1190): Annotation:keyDispatchingTimedOut I/ActivityManager(1190): CPU usage: I/ActivityManager( 1190):Load: 11.5 / 11.1 / 11.09 I/ActivityManager(1190): CPU usage from 9046ms to 4018ms ago: I/ActivityManager( 1190): d.process.acore:98% = 97% user + 0% kernel / faults: 1134 minor I/ActivityManager( 1190): system_server: 0% = 0% user + 0% kernel /faults: 1 minor I/ActivityManager( 1190): adbd:0% = 0% user + 0% kernel I/ActivityManager(1190): logcat: 0% = 0% user + 0% kernel I/ActivityManager( 1190): TOTAL:100% = 98% user + 1% kernel Cmdline: android.process.acore DALVIK THREADS: "main"prio=5 tid=3 VMWAIT |group="main" sCount=1 dsCount=0 s=N obj=0x40026240self=0xbda8 | sysTid=1815 nice=0 sched=0/0 cgrp=unknownhandle=-1344001376 atdalvik.system.VMRuntime.trackExternalAllocation(NativeMethod) atandroid.graphics.Bitmap.nativeCreate(Native Method) atandroid.graphics.Bitmap.createBitmap(Bitmap.java:468) atandroid.view.View.buildDrawingCache(View.java:6324) atandroid.view.View.getDrawingCache(View.java:6178) atandroid.view.ViewGroup.drawChild(ViewGroup.java:1541) …… atcom.android.internal.policy.impl.PhoneWindow$DecorView.draw(PhoneWindow.java:1830) atandroid.view.ViewRoot.draw(ViewRoot.java:1349) atandroid.view.ViewRoot.performTraversals(ViewRoot.java:1114) atandroid.view.ViewRoot.handleMessage(ViewRoot.java:1633) atandroid.os.Handler.dispatchMessage(Handler.java:99) atandroid.os.Looper.loop(Looper.java:123) atandroid.app.ActivityThread.main(ActivityThread.java:4370) atjava.lang.reflect.Method.invokeNative(Native Method) atjava.lang.reflect.Method.invoke(Method.java:521) atcom.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868) atcom.android.internal.os.ZygoteInit.main(ZygoteInit.java:626) atdalvik.system.NativeStart.main(Native Method) "Thread-408"prio=5 tid=329 WAIT |group="main" sCount=1 dsCount=0 s=N obj=0x46910d40self=0xcd0548 | sysTid=10602 nice=0 sched=0/0 cgrp=unknownhandle=15470792 at java.lang.Object.wait(Native Method) -waiting on <0x468cd420> (a java.lang.Object) atjava.lang.Object.wait(Object.java:288) atcom.android.dialer.CallLogContentHelper$UiUpdaterExecutor$1.run(CallLogContentHelper.java:289) atjava.lang.Thread.run(Thread.java:1096)
分析:
atdalvik.system.VMRuntime.trackExternalAllocation(NativeMethod)內存不足導致block在創建bitmap上
*MEMINFO in pid 1360 [android.process.acore] *
native dalvik other total
size: 17036 23111 N/A 40147
allocated: 16484 20675 N/A 37159
free: 296 2436 N/A 2732
解決:如果機器的內存族,可以修改虛擬機的內存為36M或更大,不過最好是復查代碼,查看哪些內存沒有釋放
很多時候需要先判斷當前用戶的網絡,才會繼續之後的一些處理邏輯。但網絡類型獲取這一塊,我用我自己的的手機調試時遇到一些問題,這裡記錄一下。一加手機一代,移動4G 網絡,得到
狀態模式說明“狀態模式允許一個對象在其內部狀態改變的時候改變其行為。這個對象看上去就像是改變了它的類一樣。” –《JAVA與模式》管理
在即時聊天中可能會存在一個隱藏的Bug,這個Bug根據手機的網速和性能有關系,比如你即時聊天中,你發送一消息,你的網絡情況不是很好,這個時候你發送的消息一直處於
本文實例為大家分享了Chronometer實現倒計時功能,Android提供了實現按照秒計時的API,供大家參考,具體內容如下一、自定義ChronometerView 繼