I get this error on the Lollipop 5.0 Nexus.
This is all i get
Fatal signal 11 (SIGSEGV), code 1 0x999e000c
I get this error when I am trying to record using AudioRecorder class of Android.
I used NDK Stack to dump the crash and I am getting the following logs.
********** Crash dump: **********
Build fingerprint: 'google/hammerhead/hammerhead:5.0/LRX21O/1570415:user/release-keys'
pid: 1752, tid: 2184, name: pool-15-thread- >>> de.shopnow <<<
signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x9b6d2000
Stack frame #00 pc 00012f1c /system/lib/libc.so (__memcpy_base+95)
Stack frame #01 pc 000569b3 /system/lib/libmedia.so (android::AudioRecord::read(void*, unsigned int)+82)
Stack frame #02 pc 00095dbb /system/lib/libandroid_runtime.so
Stack frame #03 pc 00270fd7 /data/dalvik-cache/arm/system#framework#boot.oat
Has anyone experienced this?
I have faced and fixed this issue. This might be happening because of Hardware Acceleration. Go through this link for more details: http://developer.android.com/guide/topics/graphics/hardware-accel.html
Related
I have integrated Huawei Crash Service as per documentation, and I am able to see NDK crashes in web console. However, the addresses in reports are offsetted by 4, so when I want to symbolicate crash, I get wrong result.
For example, in logcat I can see
2020-12-10 15:23:51.981 5914-5914/? D/formatEventInfo: statck
#00 pc 00c57c10 /data/app/package-name-w5yGIc9ek_yTyk1ARvNP-w==/lib/arm64/libName.so(std::set_unexpected(void (*)())) [arm64-v8a::]
#01 pc 00c57d88 /data/app/package-name-w5yGIc9ek_yTyk1ARvNP-w==/lib/arm64/libName.so(unknow) [arm64-v8a::]
#02 pc 00c54b54 /data/app/package-name-w5yGIc9ek_yTyk1ARvNP-w==/lib/arm64/libName.so(unknow) [arm64-v8a::]
#03 pc 00c5425c /data/app/package-name-w5yGIc9ek_yTyk1ARvNP-w==/lib/arm64/libName.so(__cxa_get_exception_ptr) [arm64-v8a::]
#04 pc 00c541dc /data/app/package-name-w5yGIc9ek_yTyk1ARvNP-w==/lib/arm64/libName.so(unknow) [arm64-v8a::]
and that addresses appear in web console, while valid logcat crash stack trace is
--------- beginning of crash
2020-12-10 15:23:52.067 6246-6246/? I/crash_dump64: obtaining output fd from tombstoned, type: kDebuggerdTombstone
2020-12-10 15:23:52.068 871-871/? I//system/bin/tombstoned: received crash request for pid 5914
2020-12-10 15:23:52.069 6246-6246/? I/crash_dump64: performing dump of process 5914 (target tid = 5914)
2020-12-10 15:23:52.099 6246-6246/? A/DEBUG: pid: 5914, tid: 5914, name: o.a.b >>> package-name <<<
2020-12-10 15:23:52.104 6246-6246/? A/DEBUG: #01 pc 0000000000c57c0c /data/app/package-name-w5yGIc9ek_yTyk1ARvNP-w==/lib/arm64/libName.so
2020-12-10 15:23:52.104 6246-6246/? A/DEBUG: #02 pc 0000000000c57d84 /data/app/package-name-w5yGIc9ek_yTyk1ARvNP-w==/lib/arm64/libName.so
2020-12-10 15:23:52.104 6246-6246/? A/DEBUG: #03 pc 0000000000c54b50 /data/app/package-name-w5yGIc9ek_yTyk1ARvNP-w==/lib/arm64/libName.so
2020-12-10 15:23:52.104 6246-6246/? A/DEBUG: #04 pc 0000000000c54258 /data/app/package-name-w5yGIc9ek_yTyk1ARvNP-w==/lib/arm64/libName.so
2020-12-10 15:23:52.104 6246-6246/? A/DEBUG: #05 pc 0000000000c541d8 /data/app/package-name-w5yGIc9ek_yTyk1ARvNP-w==/lib/arm64/libName.so (__cxa_throw+120)
Any ideas?
The Crash Report you got is correct. Line numbers (00c57c10, 00c57c0c, etc) do not need to be exactly matched. Because an address segment is a range, for example, your 00c57c10 and the c57c0c are may in the same address of your file. If you upload the native symbol file, you may get a readable crash report.
Here you can see an example: Obtaining an NDK Crash Report
It seems you lost your uuid because of some mistakes of your files: [arm64-v8a::];[arm64-v8a::]... They should be with uuid.
Documentation of the AppGallery Connect Crash service
In Google Play I have daily crash reporting ever-increasing.
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)
Java_org_cocos2dx_lib_Cocos2dxRenderer_nativeOnPause
backtrace:
pid: 0, tid: 0 >>> com.Feelinglucky.swipelight <<<
backtrace:
#00 pc 00000000002ca46c /data/app/com.Feelinglucky.swipelight-2/lib/arm/libplayer.so (Java_org_cocos2dx_lib_Cocos2dxRenderer_nativeOnPause+7)
#01 pc 0000000001c0c02d /data/app/com.Feelinglucky.swipelight-2/oat/arm/base.odex
How can i solve this problem? Thanks in advance
Ndk-stack give this output:
Build fingerprint: 'intel/inet_alc5651_64/inet_alc5651:5.1.1/LMY47V/inet-soft0504291459:userdebug/release-keys'
pid: 30534, tid: 30557, name: GLThread 2273 >>> xxx <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x18
Stack frame #00 pc 001a26a3 [anon:Mem_0x20000000]
Stack frame #01 pc 0000302f [anon:Mem_0x10002002]
It is not obvious. I could not find error memory address. Why is this output like above ?
Build fingerprint: GiONEE/F103/GiONEE_GBL7319:5.0/LRX21M/1433132360:user/release-keys
pid: 28431, tid: 28459 >>> com.lily.web <<<
signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr d3b0f000
#00 pc 0x0 /data/data/***/jars_fusion.dex (???)
#01 pc 0xa1eb7 /system/lib/libart.so (???)
#02 pc 0xb1cc8 [heap] (???)
java.lang.Throwable:
******* Java stack for JNI crash *******
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.lily.web.DexLoader.invokeStaticMethod(SourceFile:70)
at com.lily.web.t.<init>(SourceFile:77)
at com.lily.web.d.o(SourceFile:250)
at com.lily.web.e$2.run(SourceFile:1090)
And the related code is as following:
public Object invokeStaticMethod(String className, String methodName, Class<?>[] parameterTypes, Object... args)
{
try {
Method method = mClassLoader.loadClass(className).getMethod(methodName, parameterTypes);
method.setAccessible(true);
return method.**invoke**(null, args);
} catch {...}
}
Another stack trace:
Build fingerprint: htc/htccn_chs_cu/htc_a5dug:5.0.2/LRX22G/510432.3:user/release-keys
pid: 11542, tid: 11613 >>> com.lily.web:tools <<<
signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 90876000
#00 pc 0x0 /data/data/com.lily.web/jars_dex.dex (???)
#01 pc 0xa0a47 /system/lib/libart.so (???)
#02 pc 0xf4f49 /data/dalvik-cache/arm/system#framework#boot.oat (oatexec+1003337)
java.lang.Throwable:
******* Java stack for JNI crash *******
at java.lang.reflect.Method.**invoke**(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
As you can see, jars_fusion.dex is a big dex file of our app on Android platform. And there is a JNI crash while invoking a method in that dex, although the method is found successfully in the dex. Moreover, this issue can not be reproduced by my device or our testers, but is reported from crash auto collector system.
So what it can be the real cause of the issue, or it is just a system fault?
my android crashes sometimes for some of the users which i am able to see google developer console.
Below is the crash log for the entire crash which i extracted out of google break pad. The crash clearly says that in the following function
js_cocos2dx_TextFieldTTF_textFieldWithPlaceHolder
but i am not able to uderstand as to why this is happening. I am currently using cocos2dx-js v 3.5.
Any help or idea as to why this crash happens would be highly useful.
Build fingerprint: 'motorola/falcon_bwaca/falcon_umts:4.4.4/KXB21.14-L1.50-1/1:user/release-keys'
pid: 30910, tid: 31705, name: Thread-6337 >>> in..test <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
Stack frame #00 pc 00022160 /system/lib/libc.so (tgkill+12)
Stack frame #01 pc 000131b1 /system/lib/libc.so (pthread_kill+48)
Stack frame #02 pc 000133c5 /system/lib/libc.so (raise+10)
Stack frame #03 pc 000120fb /system/lib/libc.so
Stack frame #04 pc 00021a14 /system/lib/libc.so (abort+4)
Stack frame #05 pc 00c41251 libcocos2djs.so (__gnu_cxx::__verbose_terminate_handler()+228): Routine js_cocos2dx_TextFieldTTF_textFieldWithPlaceHolder(JSContext*, unsigned int, JS::Value*) at jsb_cocos2dx_auto.cpp:60716