• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Android app crashing on device

A

abhay_bc

Newbie
Hi I have an android app (com.first.FirstActivity) that is taking long time to launch, and eventually crashing on the device. Here is part of what adb logcat shows .. How do I analyse this log ? Can anyone point out what's happening ? Is it running out of heap ?


.....
.....
.....
.....
W/ActivityManager( 1403): Launch timeout has expired, giving up wake lock!
W/ActivityManager( 1403): Activity idle timeout for HistoryRecord{486572e0 com.first/.FirstActivity}
.....
.....
.....
.....
I/DEBUG ( 1280): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 1280): Build fingerprint: 'samsung/GT-I9003/GT-I9003/GT-I9003:2.2.1/FROYO/XXKB3:user/release-keys'
I/DEBUG ( 1280): pid: 11341, tid: 11341 >>> com.first <<<
I/DEBUG ( 1280): signal 11 (SIGSEGV), fault addr 0000004c
I/DEBUG ( 1280): r0 00000000 r1 4831de40 r2 00000000 r3 00000000
I/DEBUG ( 1280): r4 809a2400 r5 00240d00 r6 00000000 r7 0000cd28
I/DEBUG ( 1280): r8 80917040 r9 0000cd28 10 430cb970 fp bea15728
I/DEBUG ( 1280): ip 00000000 sp bea153a8 lr 809681f7 pc 8096809c cpsr 80000070
I/DEBUG ( 1280): d0 65643a64696f7262 d1 0065006400610075
I/DEBUG ( 1280): d2 4ba11af200000567 d3 000000004b815b67
I/DEBUG ( 1280): d4 0065007400730079 d5 00610050002e006d
I/DEBUG ( 1280): d6 006c004300680074 d7 3eaaaaab3f800000
I/DEBUG ( 1280): d8 0000000000000000 d9 0000000000000000
I/DEBUG ( 1280): d10 0000000000000000 d11 0000000000000000
I/DEBUG ( 1280): d12 0000000000000000 d13 0000000000000000
I/DEBUG ( 1280): d14 0000000000000000 d15 0000000000000000
I/DEBUG ( 1280): d16 ade4622100000000 d17 0064002f005b0072
I/DEBUG ( 1280): d18 002f006100740061 d19 002f007000700061
I/DEBUG ( 1280): d20 0073002e006b0069 d21 0065007400730079
I/DEBUG ( 1280): d22 00610050002e006d d23 006c004300680074
I/DEBUG ( 1280): d24 3ff0000000000000 d25 0000000000000000
I/DEBUG ( 1280): d26 0000000000000000 d27 0000000000000000
I/DEBUG ( 1280): d28 0000000000000000 d29 0000000000000000
I/DEBUG ( 1280): d30 0000000000000000 d31 0000000000000000
I/DEBUG ( 1280): scr 80000012
I/DEBUG ( 1280):
I/DEBUG ( 1280): #00 pc 0006809c /system/lib/libdvm.so
I/DEBUG ( 1280): #01 pc 000681f2 /system/lib/libdvm.so
I/DEBUG ( 1280): #02 pc 00068238 /system/lib/libdvm.so
I/DEBUG ( 1280): #03 pc 000690a6 /system/lib/libdvm.so
I/DEBUG ( 1280): #04 pc 00061a0c /system/lib/libdvm.so
I/DEBUG ( 1280): #05 pc 00063f1a /system/lib/libdvm.so
I/DEBUG ( 1280): #06 pc 0001bdd8 /system/lib/libdvm.so
I/DEBUG ( 1280): #07 pc 000227d4 /system/lib/libdvm.so
I/DEBUG ( 1280): #08 pc 00021674 /system/lib/libdvm.so
I/DEBUG ( 1280): #09 pc 0005c7d6 /system/lib/libdvm.so
I/DEBUG ( 1280): #10 pc 00064ef8 /system/lib/libdvm.so
I/DEBUG ( 1280): #11 pc 0001bdd8 /system/lib/libdvm.so
I/DEBUG ( 1280): #12 pc 000227d4 /system/lib/libdvm.so
I/DEBUG ( 1280): #13 pc 00021674 /system/lib/libdvm.so
I/DEBUG ( 1280): #14 pc 0005c614 /system/lib/libdvm.so
I/DEBUG ( 1280): #15 pc 00047cd6 /system/lib/libdvm.so
I/DEBUG ( 1280): #16 pc 000364b4 /system/lib/libandroid_runtime.so
I/DEBUG ( 1280): #17 pc 0003808c /system/lib/libandroid_runtime.so
I/DEBUG ( 1280): #18 pc 00008ca8 /system/bin/app_process
I/DEBUG ( 1280): #19 pc 0000d404 /system/lib/libc.so
I/DEBUG ( 1280):
I/DEBUG ( 1280): code around pc:
I/DEBUG ( 1280): 8096807c 0f02f1be 2500bfd8 b0054628 bf00bdf0
I/DEBUG ( 1280): 8096808c 0003a3c8 000003a0 fffc3f91 41f0e92d
I/DEBUG ( 1280): 8096809c 4d216cc3 4606a200 18ad460f d0384299
I/DEBUG ( 1280): 809680ac e078f8df 400ef855 208cf8d4 0014f112
I/DEBUG ( 1280): 809680bc eb0cf7ae c094f8d4 f1bc6a73 bf180100
I/DEBUG ( 1280):
I/DEBUG ( 1280): code around lr:
I/DEBUG ( 1280): 809681d4 461a9905 633e1820 fb12f7d9 46089902
I/DEBUG ( 1280): 809681e4 f7e84639 e004faa7 99044610 f7ff4616
I/DEBUG ( 1280): 809681f4 9803ff51 f7e82100 4628fa9d ed6af7ae
I/DEBUG ( 1280): 80968204 b0094630 bf00bdf0 0003a2c8 fffe46a4
I/DEBUG ( 1280): 80968214 ffff026e ffff1926 fffe2288 ffff194c
I/DEBUG ( 1280):
I/DEBUG ( 1280): stack:
I/DEBUG ( 1280): bea15368 430faf80 /dev/ashmem/dalvik-LinearAlloc (deleted)
I/DEBUG ( 1280): bea1536c 0000cd28 [heap]
I/DEBUG ( 1280): bea15370 bea153c4 [stack]
I/DEBUG ( 1280): bea15374 8095c61d /system/lib/libdvm.so
I/DEBUG ( 1280): bea15378 8099266e /system/lib/libdvm.so
I/DEBUG ( 1280): bea1537c 4831de40 /dev/ashmem/mspace/dalvik-heap/2 (deleted)
I/DEBUG ( 1280): bea15380 439121ed /system/framework/core.odex
I/DEBUG ( 1280): bea15384 00000000
I/DEBUG ( 1280): bea15388 bea15340 [stack]
I/DEBUG ( 1280): bea1538c 0000001f
I/DEBUG ( 1280): bea15390 80993d3a /system/lib/libdvm.so
I/DEBUG ( 1280): bea15394 809a2400 /system/lib/libdvm.so
I/DEBUG ( 1280): bea15398 00240d00 [heap]
I/DEBUG ( 1280): bea1539c 00000000
I/DEBUG ( 1280): bea153a0 df002777
I/DEBUG ( 1280): bea153a4 e3a070ad
I/DEBUG ( 1280): #00 bea153a8 809a2400 /system/lib/libdvm.so
I/DEBUG ( 1280): bea153ac 00240d00 [heap]
I/DEBUG ( 1280): bea153b0 00000000
I/DEBUG ( 1280): bea153b4 0000cd28 [heap]
I/DEBUG ( 1280): bea153b8 80917040 /system/lib/libdvm.so
I/DEBUG ( 1280): bea153bc 809681f7 /system/lib/libdvm.so
I/DEBUG ( 1280): #01 bea153c0 4867acc0 /dev/ashmem/mspace/dalvik-heap/2 (deleted)
I/DEBUG ( 1280): bea153c4 400092d0 /dev/ashmem/mspace/dalvik-heap/zygote/0 (deleted)
I/DEBUG ( 1280): bea153c8 00000000
I/DEBUG ( 1280): bea153cc 4867acc0 /dev/ashmem/mspace/dalvik-heap/2 (deleted)
I/DEBUG ( 1280): bea153d0 4831de40 /dev/ashmem/mspace/dalvik-heap/2 (deleted)
I/DEBUG ( 1280): bea153d4 00240ce8 [heap]
I/DEBUG ( 1280): bea153d8 00000000
I/DEBUG ( 1280): bea153dc ade46221 /system/lib/libicuuc.so
I/DEBUG ( 1280): bea153e0 00000001
I/DEBUG ( 1280): bea153e4 00240ce8 [heap]
I/DEBUG ( 1280): bea153e8 4831de40 /dev/ashmem/mspace/dalvik-heap/2 (deleted)
I/DEBUG ( 1280): bea153ec 809a2400 /system/lib/libdvm.so
I/DEBUG ( 1280): bea153f0 00240cd0 [heap]
I/DEBUG ( 1280): bea153f4 8096823d /system/lib/libdvm.so
 
I tried reproducing this issue on android emulator and I am getting exact same problem. I tried increasing the heap size of the emulator in steps from default 24 mb upto 400 mb, but it failed everytime with the same error. Appeared that more the memory, the crash was delayed .. but eventually it crashed in all cases. I am not able to go beyond 500 mb for heap in emulator settings since emulator fails to start with this setting .... any clues folks ?

-abhay
 
You must log in or register to reply here.
Back
Top Bottom