Android Bug 第一次,求思路 !(wait online...)

Solo_heart 发布于 2014/07/18 15:22
阅读 2K+
收藏 0

crashfile文件如下:

EVENT=CRASH
ID=05181a7e96e23180d1af
SN=Medfield7A2F2469
DATE=2014-06-16/10:58:29  
[size=13px]UPTIME=0000:12:40
BUILD=main_idpt2-latest-134,intel/mofd_v1_64/mofd_v1:4.4.2/KVT49L/main_idpt2-latest-134:userdebug/dev-keys,3.10.20-264008-gcb56599,buildbot@jfbld-g103,IA7260_XMM7260_V1_REV_2.0_FLASHLESS_01.1424.03,0002.00AB,0001.0003,A0B0.0015,0000.001E,0001.0003
BOARD=mofd_v1
IMEI=004402520375175
TYPE=ANR
DATA_READY=1
OPERATOR=Orange Tn
DATA0= com.android.phone
DATA1= Broadcast of Intent { act=android.intent.action.SCREEN_OFF flg=0x50000010 }
DATA2=android.os.MessageQueue.nativePollOnce android.os.MessageQueue.next android.os.Looper.loop android.app.ActivityThread.main java.lang.reflect.Method.invokeNative java.lang.reflect.Method.invoke com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run com.android.internal.os.ZygoteInit.main
DATA3=cpu:4% 
PARSER=LEGACY_PARSER
_END[/size]
=====================aplog_ANR_20140616105818====================
我自己认为重要的信息贴出来吧。

----------->搜索anr 得如下:

06-16 10:58:18.540   624   641 E ActivityManager: ANR in com.android.phone
06-16 10:58:18.540   624   641 E ActivityManager: PID: 879
06-16 10:58:18.540   624   641 E ActivityManager: Reason: Broadcast of Intent { act=android.intent.action.SCREEN_OFF flg=0x50000010 }
06-16 10:58:18.540   624   641 E ActivityManager: Load: 2.33 / 2.86 / 1.84
06-16 10:58:18.540   624   641 E ActivityManager: CPU usage from 10069ms to 41ms ago:
06-16 10:58:18.540   624   641 E ActivityManager:   6.7% 4284/com.google.android.apps.maps: 4.5% user + 2.1% kernel / faults: 139 minor
06-16 10:58:18.540   624   641 E ActivityManager:   2.8% 229/surfaceflinger: 1.2% user + 1.5% kernel
06-16 10:58:18.540   624   641 E ActivityManager:   2.2% 624/system_server: 1.9% user + 0.2% kernel / faults: 67 minor
06-16 10:58:18.540   624   641 E ActivityManager:   0.2% 697/com.ardic.android.afexservice: 0% user + 0.1% kernel / faults: 5 minor
06-16 10:58:18.540   624   641 E ActivityManager:   0% 921/com.android.launcher: 0% user + 0% kernel / faults: 96 minor
06-16 10:58:18.540   624   641 E ActivityManager:   0.1% 367/logcat: 0% user + 0.1% kernel
06-16 10:58:18.540   624   641 E ActivityManager:   0% 36/cfinteractive: 0% user + 0% kernel
06-16 10:58:18.540   624   641 E ActivityManager:   0% 122/mmcqd/0: 0% user + 0% kernel
06-16 10:58:18.540   624   641 E ActivityManager:   0% 169/dhd_dpc: 0% user + 0% kernel
06-16 10:58:18.540   624   641 E ActivityManager:   0% 226/nvm_server: 0% user + 0% kernel
06-16 10:58:18.540   624   641 E ActivityManager:   0% 227/netd: 0% user + 0% kernel / faults: 9 minor
06-16 10:58:18.540   624   641 E ActivityManager:   0% 751/com.android.systemui: 0% user + 0% kernel / faults: 21 minor
06-16 10:58:18.540   624   641 E ActivityManager:   0% 1088/com.intel.imsstack: 0% user + 0% kernel
06-16 10:58:18.540   624   641 E ActivityManager:   0% 1129/com.intel.cam: 0% user + 0% kernel / faults: 5 minor
06-16 10:58:18.540   624   641 E ActivityManager:   0% 3444/kworker/u8:18: 0% user + 0% kernel
06-16 10:58:18.540   624   641 E ActivityManager:   0% 3469/kworker/u8:43: 0% user + 0% kernel
06-16 10:58:18.540   624   641 E ActivityManager: 4% TOTAL: 2.3% user + 1.4% kernel + 0% iowait + 0.1% irq + 0% softirq
06-16 10:58:18.540   624   641 E ActivityManager: CPU usage from 2729ms to 3246ms later:
06-16 10:58:18.540   624   641 E ActivityManager:   18% 624/system_server: 9.4% user + 9.4% kernel / faults: 32 minor
06-16 10:58:18.540   624   641 E ActivityManager:     9.4% 631/Compiler: 9.4% user + 0% kernel
06-16 10:58:18.540   624   641 E ActivityManager:     5.6% 641/ActivityManager: 0% user + 5.6% kernel
06-16 10:58:18.540   624   641 E ActivityManager:     1.8% 633/FinalizerDaemon: 0% user + 1.8% kernel
06-16 10:58:18.540   624   641 E ActivityManager:     1.8% 977/Binder_8: 1.8% user + 0% kernel
06-16 10:58:18.540   624   641 E ActivityManager:   7.5% 4284/com.google.android.apps.maps: 5.6% user + 1.8% kernel / faults: 17 minor
06-16 10:58:18.540   624   641 E ActivityManager:     3.7% 4284/droid.apps.maps: 3.7% user + 0% kernel
06-16 10:58:18.540   624   641 E ActivityManager:     3.7% 4291/Compiler: 3.7% user + 0% kernel
06-16 10:58:18.540   624   641 E ActivityManager:   2.7% 229/surfaceflinger: 0% user + 2.7% kernel
06-16 10:58:18.540   624   641 E ActivityManager:     1.3% 385/EventThread: 0% user + 1.3% kernel
06-16 10:58:18.540   624   641 E ActivityManager:   1.4% 1177/com.google.process.gapps: 1.4% user + 0% kernel
06-16 10:58:18.540   624   641 E ActivityManager: 8.1% TOTAL: 5.2% user + 2.4% kernel + 0.4% irq
06-16 10:58:18.540   624   641 I ActivityManager: Killing 879:com.android.phone/1001 (adj -12): background ANR

----------->搜索am_anr 得如下:

06-16 10:58:14.820   624   641 W BroadcastQueue: Timeout of broadcast BroadcastRecord{27586430 u-1 android.intent.action.SCREEN_OFF} - receiver=android.os.BinderProxy@26f962e8, started 10000ms ago
06-16 10:58:14.820   624   641 W BroadcastQueue: Receiver during timeout: BroadcastFilter{27165080 u0 ReceiverList{27126bd8 879 com.android.phone/1001/u0 remote:26f962e8}}
06-16 10:58:14.820   624   641 I am_broadcast_discard_filter: [0,660104240,android.intent.action.SCREEN_OFF,13,655773824]
06-16 10:58:14.820   624   641 I am_anr  : [0,879,com.android.phone,1086897741,Broadcast of Intent { act=android.intent.action.SCREEN_OFF flg=0x50000010 }]
06-16 10:58:14.820   766  1694 I SecurityManagerService: SMS received security event: IPCEvent[BROADCAST_INTENT/android]{container=0}
06-16 10:58:14.820   624   641 V AsfAosp : No ASF clients are connected
06-16 10:58:14.830   624   641 I Process : Sending signal. PID: 879 SIG: 3
06-16 10:58:14.830   879   884 I dalvikvm: threadid=3: reacting to signal 3
06-16 10:58:14.900   879   884 I dalvikvm: Wrote stack traces to '/data/anr/traces.txt'
06-16 10:58:14.900   624   641 I Process : Sending signal. PID: 624 SIG: 3
06-16 10:58:14.900   624   629 I dalvikvm: threadid=3: reacting to signal 3
06-16 10:58:15.120   624   639 E Sensors : sensorPoll: line: 240 poll error: 4 Interrupted system call
06-16 10:58:15.130   624   641 I Process : Sending signal. PID: 900 SIG: 3
06-16 10:58:15.130   900   907 I dalvikvm: threadid=3: reacting to signal 3
06-16 10:58:15.130   624   629 I dalvikvm: Wrote stack traces to '/data/anr/traces.txt'
06-16 10:58:15.130   624   641 I Process : Sending signal. PID: 885 SIG: 3
06-16 10:58:15.140   885   891 I dalvikvm: threadid=3: reacting to signal 3
06-16 10:58:15.160   885   891 I dalvikvm: Wrote stack traces to '/data/anr/traces.txt'
06-16 10:58:15.160   624   641 I Process : Sending signal. PID: 751 SIG: 3
06-16 10:58:15.160   751   756 I dalvikvm: threadid=3: reacting to signal 3
06-16 10:58:15.170   900   907 I dalvikvm: Wrote stack traces to '/data/anr/traces.txt'
06-16 10:58:15.170   624   641 I Process : Sending signal. PID: 766 SIG: 3
06-16 10:58:15.170   766   771 I dalvikvm: threadid=3: reacting to signal 3
06-16 10:58:15.190   766   771 I dalvikvm: Wrote stack traces to '/data/anr/traces.txt'
06-16 10:58:15.190   624   641 I Process : Sending signal. PID: 697 SIG: 3
06-16 10:58:15.190   697   702 I dalvikvm: threadid=3: reacting to signal 3
06-16 10:58:15.210   751   756 I dalvikvm: Wrote stack traces to '/data/anr/traces.txt'
06-16 10:58:15.260   697   702 I dalvikvm: Wrote stack traces to '/data/anr/traces.txt'
06-16 10:58:17.550   624   641 D dalvikvm: GC_EXPLICIT freed 3346K, 19% free 38075K/46880K, paused 1ms+4ms, total 69ms
06-16 10:58:18.100   624   641 I Process : Sending signal. PID: 4284 SIG: 3
06-16 10:58:18.100  4284  4289 I dalvikvm: threadid=3: reacting to signal 3
06-16 10:58:18.160  4284  4289 I dalvikvm: Wrote stack traces to '/data/anr/traces.txt'
06-16 10:58:18.160   624   641 I Process : Sending signal. PID: 1177 SIG: 3
06-16 10:58:18.160  1177  1182 I dalvikvm: threadid=3: reacting to signal 3
06-16 10:58:18.200  1177  1182 I dalvikvm: Wrote stack traces to '/data/anr/traces.txt'
嗯,就怎么多吧,还有好几个文件的,不知道怎么分析,不忙的大神告诉我分析的过程吧。

不求解决这个问题,只求一个分析这个问题的方法思路。(在线等。。。)

加载中
0
S
Solo_heart

好吧,我先说说的的想法吧。

我看到crashfile文件DATA2=android.os.MessageQueue.nativePollOnce android.os.MessageQueue.next,然后我认为是不是在广播的时候,消息队列里正好有消息,然后开始从消息队列中取出消息?

是不是这样??

返回顶部
顶部