android - Native crash in unknown unknown -


i have app entirely written in java - no native code whatsoever - , i've twice had crash report on developer console "native crash in unknown unknown". have no idea start locating source of problem. searching has revealed type of crash in case of android bugs, ndk usage or buggy third party libraries.

for it's worth, here 1 of logs:

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** build fingerprint: 'samsung/m0xx/m0:4.3/jss15j/i9300xxugmj9:user/release-keys' revision: '12' pid: 2197, tid: 2197, name: .test.app >>> com.test.app <<< signal 6 (sigabrt), code -6 (si_tkill), fault addr -------- r0 fffffffc r1 bef3f3f8 r2 00000010 r3 ffffffff r4 41619610 r5 00000000 r6 41619624 r7 000000fc r8 41619658 r9 00000014 sl 418cc238 fp bef3f56c ip bef3f3f8 sp bef3f3d8 lr 40115045 pc 401a1574 cpsr 280b0010 d0 0000000100110102 d1 0000000044a01000 d2 0000000000000000 d3 0000000000000000 d4 000002d044340000 d5 0000000042a40000 d6 0000000000000000 d7 000000003f800000 d8 0000000000000030 d9 4301000000000000 d10 0000000042400000 d11 0000000000000000 d12 0000000000000000 d13 0000000000000000 d14 0000000000000000 d15 0000000000000000 d16 00002bdd67c11c72 d17 0000000000000000 d18 0000000000000000 d19 2200220022002200 d20 0000000000000003 d21 0000000000000003 d22 0000000000000002 d23 0000000000000003 d24 2222222222222224 d25 2222222222222224 d26 2222222222222223 d27 ffffffffffffffff d28 01000100010000fd d29 0100010001000100 d30 0100010001000100 d31 0100010001000100 scr 60000010  backtrace: #00 pc 0001c574 /system/lib/libc.so (epoll_wait+12) #01 pc 00015041 /system/lib/libutils.so (android::looper::pollinner(int)+92) #02 pc 00015261 /system/lib/libutils.so (android::looper::pollonce(int, int*, int*, void**)+92) #03 pc 0006bd21 /system/lib/libandroid_runtime.so (android::nativemessagequeue::pollonce(_jnienv*, int)+22) #04 pc 0001eb0c /system/lib/libdvm.so (dvmplatforminvoke+112) #05 pc 0004f457 /system/lib/libdvm.so (dvmcalljnimethod(unsigned int const*, jvalue*, method const*, thread*)+398) #06 pc 00027fa0 /system/lib/libdvm.so #07 pc 0002c9d0 /system/lib/libdvm.so (dvminterpret(thread*, method const*, jvalue*)+184) #08 pc 0006176b /system/lib/libdvm.so (dvminvokemethod(object*, method const*, arrayobject*, arrayobject*, classobject*, bool)+350) #09 pc 0006944b /system/lib/libdvm.so #10 pc 00027fa0 /system/lib/libdvm.so #11 pc 0002c9d0 /system/lib/libdvm.so (dvminterpret(thread*, method const*, jvalue*)+184) #12 pc 000614ad /system/lib/libdvm.so (dvmcallmethodv(thread*, method const*, object*, bool, jvalue*, std::__va_list)+292) #13 pc 0004b03b /system/lib/libdvm.so #14 pc 0004f5e7 /system/lib/libandroid_runtime.so #15 pc 00050277 /system/lib/libandroid_runtime.so (android::androidruntime::start(char const*, char const*)+378) #16 pc 0000105b /system/bin/app_process #17 pc 0000dd03 /system/lib/libc.so (__libc_init+50) #18 pc 00000d7c /system/bin/app_process  code around pc: 401a1554 e1a0700c e3700a01 912fff1e e2600000  401a1564 ea007f30 e1a0c007 e3a070fc ef000000  401a1574 e1a0700c e3700a01 912fff1e e2600000  401a1584 ea007f28 e1a0c007 e3a07f4f ef000000  401a1594 e1a0700c e3700a01 912fff1e e2600000  401a15a4 ea007f20 e1a0c007 e59f7014 ef000000  401a15b4 e1a0700c e3700a01 912fff1e e2600000  401a15c4 ea007f18 0000013d e1a0c007 e59f7014  401a15d4 ef000000 e1a0700c e3700a01 912fff1e  401a15e4 e2600000 ea007f0f 0000013e e1a0c007  401a15f4 e3a070a8 ef000000 e1a0700c e3700a01  401a1604 912fff1e e2600000 ea007f06 e1a0c007  401a1614 e3a07f59 ef000000 e1a0700c e3700a01  401a1624 912fff1e e2600000 ea007efe e1a0c007  401a1634 e59f7014 ef000000 e1a0700c e3700a01  401a1644 912fff1e e2600000 ea007ef6 000f0005   code around lr: 40115024 0848f104 46402500 f7fdaf08 2210fd8e  40115034 46394633 6b2065e5 0614f104 eeaaf7f7  40115044 46304681 feb6f7f8 da1245a9 ece6f7f7  40115054 2f046807 f04fd102 e05637ff f06f4962  40115064 4a620703 20056803 447a4479 ec52f7f7  40115074 d048e04b a178f8df b178f8df 44fa4b5e  40115084 447b44fb 01289305 583b1839 68e0688a  40115094 d10c4282 d50307d9 f7ff4620 e02efdf1  401150a4 20054a56 447a4659 ec34f7f7 4611e027  401150b4 0034f104 92049303 ff0df7ff 99042800  401150c4 db169b03 0101f003 bf48075a 0102f041  401150d4 bf48071a 0104f041 6ba306db f041bf48  401150e4 22140108 3300fb02 1d1a4620 ff5bf7ff  401150f4 9100e005 99052005 f7f74652 3501ec0c  40115104 dbc0454d f06fe7a7 f04f0702 f06f32ff  40115114 e9c44300 f1042318 e02f0918 f7fc2001  

any suggestions next steps? have own logfile it's nothing granular enough have tracked this.

searching has revealed type of crash in case of android bugs, ndk usage or buggy third party libraries

the fourth scenario buggy roms, whether roms stock roms manufacturer or rom mods (e.g., cyanogenmod). once-in-a-blue-moon sorts of crashes come rom issues, otherwise run them more often.

any suggestions next steps?

for couple of users, wouldn't worry.

otherwise, build fingerprint give idea of environment working with. in case, samsung/m0xx appear samsung gt-i9300, 1 of "galaxy s3" variants. if can hands on 1 of -- whether via outright purchase, online testing service, or borrowing friend -- see if can reproduce crash , narrow down in code crash coming from. if can that, perhaps can come workaround either fine devices, or @ least gets past crash on one.


Comments

Popular posts from this blog

android - Get AccessToken using signpost OAuth without opening a browser (Two legged Oauth) -

org.mockito.exceptions.misusing.InvalidUseOfMatchersException: mockito -

google shop client API returns 400 bad request error while adding an item -