Hello guys ,this is just a request,does anyone know how to solve issue with xiaomi redmi 7A apps crashing?!It has android 10 and miui 12.0.1 update.
It gives this error message:
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'Xiaomi/pine/pine:10/QKQ1.191014.001/V12.0.1.0.QCMMIXM:user/release-keys'
Revision: '0'
ABI: 'arm'
Timestamp: 2021-03-23 04:46:54+0100
pid: 9437, tid: 9437, name: miui.msa.global >>> com.miui.msa.global <<<
uid: 10111
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
Cause: null pointer dereference
r0 beeab4fc r1 85e834da r2 00000000 r3 00000006
r4 00000003 r5 00000000 r6 beeab4fc r7 3c444a70
r8 897cace4 r9 3c427064 r10 3c42706c r11 3c408088
ip 00000002 sp beeab4f8 lr 877b4ba1 pc 8840ceba
backtrace:
#00 pc 02919eba /data/app/com.google.android.trichromelibrary_438909030-5XbUikOv66vxlsu1GzkAwQ==/base.apk!libmonochrome.so (offset 0x645000) (BuildId: 98fedb7d52a7c50d74bd90494d1bac32f1fc82e9)
Related
I am having a crash when I try to view emails on the stock app. I am having this logcat;
Code:
[ 12-12 18:33:56.046 1094: 1094 D/CrashAnrDetector ]
Build: samsung/serranoltexx/serranolte:4.4.2/KOT49H/I9195XXUCNJ4:user/release-keys
Hardware: MSM8960
Revision: 5
Bootloader: I9195XXUCNH5
Radio: unknown
Kernel: Linux version 3.4.0-brisK-g1091455 ([email protected]) (gcc version 4.7.4 (crosstool-NG linaro-1.13.1+bzr2694 - Linaro GCC 2014.06 - Cortex-A15) ) #1 SMP Sun Dec 7 14:49:19 CET 2014
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'samsung/serranoltexx/serranolte:4.4.2/KOT49H/I9195XXUCNJ4:user/release-keys'
Revision: '5'
pid: 17632, tid: 17818, name: WebViewCoreThre >>> com.android.email <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000004
r0 00000004 r1 659b6ea0 r2 00000004 r3 00000004
r4 00000000 r5 669e6828 r6 00000000 r7 00000000
r8 653ff3d8 r9 64e65fd0 sl 00000000 fp 00000001
ip 40647b18 sp 659b6e00 lr 4055781b pc 4017761c cpsr 000f0010
d0 408000003f800000 d1 0000000000000000
d2 0000000000000000 d3 0000000000000000
d4 7767574737f6e6d6 d5 f7e7d7c7b7a79787
d6 0000000002020011 d7 0000000000000000
d8 3fa999999999999a d9 41d522c9c0abf4f9
d10 0000000000000000 d11 0000000000000000
d12 8080808080808080 d13 0000000000000000
d14 0000000000000000 d15 0000000000000000
d16 006c00690061006d d17 0072006600200073
d18 0073006c00690061 d19 00200072006f0020
d20 00200075006f0079 d21 006c0020006f006e
d22 00650067006e006f d23 0077000a00200072
d24 4024000000000000 d25 0000000000000000
d26 4025931319798d6e d27 4059000000000000
d28 4024000000000000 d29 4059000000000000
d30 3ff0000000000000 d31 4082c00000000000
scr 68000013
backtrace:
#00 pc 0000361c /system/lib/libcutils.so (android_atomic_inc+8)
#01 pc 000cc817 /system/lib/libskia.so (SkString::RefRec(SkString::Rec*)+14)
#02 pc 000cc877 /system/lib/libskia.so (SkString::SkString(SkString const&)+6)
#03 pc 001b2c45 /system/lib/libwebcore.so
#04 pc 001b2843 /system/lib/libwebcore.so
#05 pc 001aa363 /system/lib/libwebcore.so
#06 pc 003ac38d /system/lib/libwebcore.so
#07 pc 003acfd3 /system/lib/libwebcore.so
#08 pc 0018c227 /system/lib/libwebcore.so
#09 pc 001d020b /system/lib/libwebcore.so
#10 pc 001e0977 /system/lib/libwebcore.so
#11 pc 001dbca9 /system/lib/libwebcore.so
#12 pc 001d03e1 /system/lib/libwebcore.so
#13 pc 001d9855 /system/lib/libwebcore.so
#14 pc 001daf05 /system/lib/libwebcore.so
#15 pc 001dbcb1 /system/lib/libwebcore.so
#16 pc 001d03e1 /system/lib/libwebcore.so
#17 pc 001d9855 /system/lib/libwebcore.so
#18 pc 001daf05 /system/lib/libwebcore.so
#19 pc 001dbcb1 /system/lib/libwebcore.so
#20 pc 001d03e1 /system/lib/libwebcore.so
#21 pc 001d9855 /system/lib/libwebcore.so
#22 pc 001daf05 /system/lib/libwebcore.so
#23 pc 001dbcb1 /system/lib/libwebcore.so
#24 pc 001d03e1 /system/lib/libwebcore.so
#25 pc 001d9855 /system/lib/libwebcore.so
#26 pc 001daf05 /system/lib/libwebcore.so
#27 pc 001dbcb1 /system/lib/libwebcore.so
#28 pc 001d03e1 /system/lib/libwebcore.so
#29 pc 00225dc3 /system/lib/libwebcore.so
#30 pc 00173bfb /system/lib/libwebcore.so
#31 pc 0033faeb /system/lib/libwebcore.so
stack:
659b6dc0 659b6dd0 [stack:17818]
659b6dc4 6103fc91 /system/lib/libwebcore.so
659b6dc8 00000001
659b6dcc 6103fdfd /system/lib/libwebcore.so
659b6dd0 00000000
659b6dd4 00000000
659b6dd8 00000000
659b6ddc 7e8a0000
659b6de0 00000000
659b6de4 00000000
659b6de8 648fb680
659b6dec 6103fea9 /system/lib/libwebcore.so
659b6df0 67a65c68
659b6df4 659b6e7c [stack:17818]
659b6df8 00000000
659b6dfc 61040b8b /system/lib/libwebcore.so
#00 659b6e00 659b6e14 [stack:17818]
........ ........
#01 659b6e00 659b6e14 [stack:17818]
659b6e04 40557
[ 12-12 18:33:56.046 1094: 1094 D/CrashAnrDetector ]
processName:com.android.email
[ 12-12 18:33:56.056 1094: 1094 D/CrashAnrDetector ]
broadcastEvent : com.android.email SYSTEM_TOMBSTONE
I have tried replacing libwebcore.so with another version, but I still have the crash.
Would appreciate any help provided.
Kind regards,
Hi,
As a senior member of XDA, you should know to always read the stickies at the top of sections, like this one in the Assist section,
> General discussion > XDA Assist > The Purpose of XDA Assist [Please Read]
So please ask about this in your device section.
Thanks for understanding, thread closed.
Hello!
I have recently bought a Xiaomi Redmi Note wcdma device
When device came he had a faulty updater so i've decided to update the firmware to the latest firm available (via recovery). Before and after the update the device had the same problems: random reboots and some app/sometimes froze the phone.
So i flashed a rom via fastboot with spflash. I had the same problems.
The curent version that i am using is Official Stable Multilanguage WCDMA MIUI v5 39.0.0
I got system freeze when i was trying to clean recent apps and when i played Shadow Fight 2.
In the last case was a softreboot that i have succesfully catched in a logcat.
Code:
02-07 08:11:05.660 F/libc ( 160): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 160 (surfaceflinger)
02-07 08:11:05.662 F/libc ( 160): Send stop signal to pid:160 in debugger_signal_handler
02-07 08:11:05.662 I/DEBUG (13437): handle_request(16)
02-07 08:11:05.662 I/DEBUG (13437): check process 160 name:surfaceflinger
02-07 08:11:05.664 I/DEBUG (13437): BOOM: pid=160 uid=1000 gid=1000 tid=160
02-07 08:11:05.666 I/DEBUG (13437): [OnPurpose Redunant in preset_info] pid: 160, tid: 160, name: surfaceflinger >>> <<<
02-07 08:11:05.780 I/DEBUG (13437): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
02-07 08:11:05.781 I/DEBUG (13437): Build fingerprint: 'Xiaomi/lcsh92_wet_jb9/lcsh92_wet_jb9:4.2.2/JDQ39/JHDCNBL39.0:user/release-keys'
02-07 08:11:05.781 I/DEBUG (13437): pid: 160, tid: 160, name: surfaceflinger >>> <<<
02-07 08:11:05.781 I/DEBUG (13437): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
My questions are :
1. What is it to be done (i have no more ideeas)?
2. Is it safe to upload the entire logcat?
Anyone ?!?
Said ahead, I would have posted this in http://forum.xda-developers.com/galaxy-s2-plus/orig-development/rom-cyanogenmod-12-1-t3084287 where it belonged, since the bug was reproduced on that ROM, if it wasn't for that stupid "You must spam 10 times before you may properly report bugs" setting on this forum.
There appears to be some crashes in Chromium in >4.4.4 ROMs, related to this:
https://code.google.com/p/chromium/...er_bug_list_json.cc&sq=package:chromium&l=913
These crashes can be triggered by aggressive scrolling in either Chromium itself or any application utilizing libwebviewchromium.so. It will produce something along the lines of:
Code:
E/chromium( 4906): [ERROR:gl_renderer.cc(466)] Reached limit of pending sync queries.
--- snip, several repetions ---
E/chromium( 4906): [ERROR:gl_renderer.cc(466)] Reached limit of pending sync queries.
E/chromium( 4906): [ERROR:gl_fence_egl.cc(34)] Failed to get EGLSync attribute. error code:12300
E/chromium( 4906): [ERROR:gl_fence_egl.cc(50)] Failed to wait for EGLSync. error:EGL_BAD_PARAMETER
F/chromium( 4906): [FATAL:gl_fence_egl.cc(52)] Check failed: g_ignore_egl_sync_failures.
W/google-breakpad( 5032): -----BEGIN BREAKPAD MICRODUMP-----
W/google-breakpad( 5032): V WebView:45.0.2454.95
--- snip ---
F/libc ( 4906): Fatal signal 6 (SIGABRT), code -6 in tid 4961 (RenderThread)
I/DEBUG ( 146): property debug.db.uid not set; NOT waiting for gdb.
I/DEBUG ( 146): HINT: adb shell setprop debug.db.uid 100000
I/DEBUG ( 146): HINT: adb forward tcp:5039 tcp:5039
I/DEBUG ( 146): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 146): Build fingerprint: 'samsung/s2vepxx/s2vep:4.2.2/JDQ39/I9105PXXUBNG1:user/release-keys'
I/DEBUG ( 146): Revision: '5'
I/DEBUG ( 146): ABI: 'arm'
I/DEBUG ( 146): pid: 4906, tid: 4961, name: RenderThread >>> com.google.android.gm <<<
I/DEBUG ( 146): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
I/DEBUG ( 146): Abort message: '[FATAL:gl_fence_egl.cc(52)] Check failed: g_ignore_egl_sync_failures.
I/DEBUG ( 146): '
I/DEBUG ( 146): r0 00000000 r1 00001361 r2 00000006 r3 00000000
I/DEBUG ( 146): r4 52ea8dd8 r5 00000006 r6 00000016 r7 0000010c
I/DEBUG ( 146): r8 402c4de4 r9 52ea7ff4 sl 00000000 fp 000001eb
I/DEBUG ( 146): ip 00001361 sp 52ea7b48 lr 40280c59 pc 402a67fc cpsr 600f0010
I/DEBUG ( 146):
I/DEBUG ( 146): backtrace:
I/DEBUG ( 146): #00 pc 000397fc /system/lib/libc.so (tgkill+12)
I/DEBUG ( 146): #01 pc 00013c55 /system/lib/libc.so (pthread_kill+52)
I/DEBUG ( 146): #02 pc 000149b3 /system/lib/libc.so (raise+10)
I/DEBUG ( 146): #03 pc 000110ed /system/lib/libc.so (__libc_android_abort+36)
I/DEBUG ( 146): #04 pc 0000f5cc /system/lib/libc.so (abort+4)
I/DEBUG ( 146): #05 pc 002b8bf9 /data/app/com.google.android.webview-1/lib/arm/libwebviewchromium.so
The "EGL_KHR_fence_sync" EGL extension is supposed to be fixed in all Broadcom based devices shipping with Android >4.4.4. Obviously this isn't the case with this platform, as the driver fix got never backported.
There is no point in reporting this upstream to the Chromium team. So .... what to do?
EDIT:
OK....
The broken extension is announced in /vendor/lib/egl/libGLES_vc4.so @0x6F78A-0x6F79C
Somebody is probably going to smack me for suggesting to fiddle around in binary content, but it looks like the sanest approach to fix the bug.
Copy 0x1F bytes from (src start) 0x6F79D to (dest start) 0x6F78A (beware of overlap when performing the copy)
Set 0x13 bytes to 0x00 at (start) 0x6F7A9
That removes the extension from the string, moves the trailing extension list forward, and fills the resulting gap with null bytes in order not to break alignment.
The extension isn't mandatory, the existing implementation is broken, so let's just get rid of that thing.
Change is not tested yet. Someone feel like trying?
EDIT2:
That thing isn't as easy to deactivate as I expected. And it turns out, it actually is a mandatory feature in EGL 1.5 ...
But if the driver isn't announcing it any longer, who is then? Broken software emulation as well?
Next step: Patching it out of libwebviewchromium.so, getting that Android <=4.4.4 workaround back in.
EDIT3:
Meh, too much work for me. Then it's back to <=4..4.4 for me. May someone else try to work around that bug.
Some of you may experience "bluetooth" not able to start after upgrading to oero (8.0) like me. It was because, your device was bricked and recovered. Bricking and restore erase your BT MAC address and Oero enforced address checking of bluetooth. And resulting errors. An wearos watch without bluetooth is essential useless, and you are not given choices to upgrade or not.
If any one has any information to fix this address, please share with us. And you are more than welcome to share your efs partition with me, I need a bluetooth version efs partition.
Code:
04-05 00:44:27.745 W//system/bin/hwservicemanager( 267): getTransportFromManifest: Cannot find entry [email protected]::IBluetoothHci in either framework or device manifest, using default transport.
04-05 00:44:27.753 I/bt_hci ( 5625): hci_initialize: IBluetoothHci::getService() returned 0xa6c63680 (local)
04-05 00:44:27.753 I/[email protected]( 5625): BluetoothHci::initialize()
04-05 00:44:27.756 D/ ( 5625): get_local_address: Trying /nvdata/MACBT
04-05 00:44:27.756 F/zygote ( 5625): bluetooth_address.cc:58] Check failed: bytes_read == kStringLength
04-05 00:44:27.757 F/libc ( 5625): Fatal signal 6 (SIGABRT), code -6 in tid 5657 (hci_thread)
04-05 00:44:27.889 I/PackageManager.DexOptimizer( 437): Running dexopt (dexoptNeeded=1) on: /data/app/vmdl136066528.tmp/base.apk pkg=com.google.android.marvin.talkback isa=arm dexoptFlags=boot_complete,public target-filter=quicken oatDir=/data/app/vmdl136066528.tmp/oat sharedLibraries=/system/framework/com.google.android.wearable.jar
04-05 00:44:27.909 I/crash_dump32( 5662): obtaining output fd from tombstoned
04-05 00:44:27.911 I//system/bin/tombstoned( 349): received crash request for pid 5625
04-05 00:44:27.923 I/crash_dump32( 5662): performing dump of process 5625 (target tid = 5657)
04-05 00:44:27.923 F/DEBUG ( 5662): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
04-05 00:44:27.924 F/DEBUG ( 5662): Build fingerprint: 'huawei/sawfish/sawfish:8.0.0/OWDD.180215.018/4632152:user/release-keys'
04-05 00:44:27.924 F/DEBUG ( 5662): Revision: '0'
04-05 00:44:27.924 F/DEBUG ( 5662): ABI: 'arm'
04-05 00:44:27.924 F/DEBUG ( 5662): pid: 5625, tid: 5657, name: hci_thread >>> com.android.bluetooth <<<
04-05 00:44:27.924 F/DEBUG ( 5662): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
04-05 00:44:27.936 F/DEBUG ( 5662): Abort message: 'bluetooth_address.cc:58] Check failed: bytes_read == kStringLength '
04-05 00:44:27.936 F/DEBUG ( 5662): r0 00000000 r1 00001619 r2 00000006 r3 00000008
04-05 00:44:27.936 F/DEBUG ( 5662): r4 000015f9 r5 00001619 r6 9ec68a60 r7 0000010c
04-05 00:44:27.936 F/DEBUG ( 5662): r8 9ec68ca0 r9 9ec68c70 sl 9ec68d18 fp 9ec68d60
04-05 00:44:27.936 F/DEBUG ( 5662): ip 00000000 sp 9ec68a50 lr b209a407 pc b20ca96c cpsr 200b0010
04-05 00:44:28.214 F/DEBUG ( 5662):
04-05 00:44:28.214 F/DEBUG ( 5662): backtrace:
04-05 00:44:28.214 F/DEBUG ( 5662): #00 pc 0004a96c /system/lib/libc.so (tgkill+12)
04-05 00:44:28.214 F/DEBUG ( 5662): #01 pc 0001a403 /system/lib/libc.so (abort+54)
04-05 00:44:28.215 F/DEBUG ( 5662): #02 pc 0000752b /system/lib/libbase.so (_ZN7android4base14DefaultAborterEPKc+6)
04-05 00:44:28.215 F/DEBUG ( 5662): #03 pc 00007e09 /system/lib/libbase.so (_ZN7android4base10LogMessageD2Ev+456)
04-05 00:44:28.215 F/DEBUG ( 5662): #04 pc 0000637b /system/vendor/lib/hw/[email protected] (_ZN7android8hardware9bluetooth4V1_014implementation16BluetoothAddress17get_local_addressEPh+378)
04-05 00:44:28.215 F/DEBUG ( 5662): #05 pc 0000685d /system/vendor/lib/hw/[email protected] (_ZN7android8hardware9bluetooth4V1_014implementation15VendorInterface4OpenENSt3__18functionIFvbEEENS6_IFvRKNS0_8hidl_vecIhEEEEESE_SE_+60)
04-05 00:44:28.215 F/DEBUG ( 5662): #06 pc 000067a1 /system/vendor/lib/hw/[email protected] (_ZN7android8hardware9bluetooth4V1_014implementation15VendorInterface10InitializeENSt3__18functionIFvbEEENS6_IFvRKNS0_8hidl_vecIhEEEEESE_SE_+136)
04-05 00:44:28.215 F/DEBUG ( 5662): #07 pc 00005303 /system/vendor/lib/hw/[email protected] (_ZN7android8hardware9bluetooth4V1_014implementation12BluetoothHci10initializeERKNS_2spINS2_22IBluetoothHciCallbacksEEE+482)
04-05 00:44:28.216 F/DEBUG ( 5662): #08 pc 00015ce7 /system/lib/[email protected] (_ZN7android8hardware9bluetooth4V1_014BsBluetoothHci10initializeERKNS_2spINS2_22IBluetoothHciCallbacksEEE+242)
04-05 00:44:28.216 F/DEBUG ( 5662): #09 pc 0009eec7 /system/lib/hw/bluetooth.default.so (_Z14hci_initializev+258)
04-05 00:44:28.216 F/DEBUG ( 5662): #10 pc 0007ed63 /system/lib/libchrome.so (_ZN4base5debug13TaskAnnotator7RunTaskEPKcRKNS_11PendingTaskE+122)
04-05 00:44:28.216 F/DEBUG ( 5662): #11 pc 0008f637 /system/lib/libchrome.so (_ZN4base11MessageLoop7RunTaskERKNS_11PendingTaskE+162)
04-05 00:44:28.216 F/DEBUG ( 5662): #12 pc 0008f825 /system/lib/libchrome.so (_ZN4base11MessageLoop21DeferOrRunPendingTaskENS_11PendingTaskE+18)
04-05 00:44:28.216 F/DEBUG ( 5662): #13 pc 0008f9ff /system/lib/libchrome.so (_ZN4base11MessageLoop6DoWorkEv+190)
04-05 00:44:28.216 F/DEBUG ( 5662): #14 pc 000907af /system/lib/libchrome.so (_ZN4base18MessagePumpDefault3RunEPNS_11MessagePump8DelegateE+26)
04-05 00:44:28.216 F/DEBUG ( 5662): #15 pc 0009f835 /system/lib/libchrome.so (_ZN4base7RunLoop3RunEv+40)
04-05 00:44:28.216 F/DEBUG ( 5662): #16 pc 0009d6d3 /system/lib/hw/bluetooth.default.so (_Z16message_loop_runPv+162)
04-05 00:44:28.217 F/DEBUG ( 5662): #17 pc 0012aeab /system/lib/hw/bluetooth.default.so (_ZL18work_queue_read_cbPv+50)
04-05 00:44:28.217 F/DEBUG ( 5662): #18 pc 00129865 /system/lib/hw/bluetooth.default.so (_ZL11run_reactorP9reactor_ti+216)
04-05 00:44:28.217 F/DEBUG ( 5662): #19 pc 00129761 /system/lib/hw/bluetooth.default.so (_Z13reactor_startP9reactor_t+44)
04-05 00:44:28.217 F/DEBUG ( 5662): #20 pc 0012aa5d /system/lib/hw/bluetooth.default.so (_ZL10run_threadPv+136)
04-05 00:44:28.217 F/DEBUG ( 5662): #21 pc 00047c8f /system/lib/libc.so (_ZL15__pthread_startPv+22)
04-05 00:44:28.217 F/DEBUG ( 5662): #22 pc 0001afad /system/lib/libc.so (__start_thread+32)
My initial though is that system would usually assign a software generated mac address for missing mac address.
But 8.0 up seems not having this feature and thus BT is not usable. On the other hand, WIFI works flawlessly.
what if you flash the nougat stock rom? would be still lost?!
Kianush said:
what if you flash the nougat stock rom? would be still lost?!
Click to expand...
Click to collapse
nougat rom will be working fine. Although the mac address are still invalid, but the system will generate a mock up mac id.
So everything is fine to use. Just that it will keep update by itself.
One more finding, if I flash directly to android P from nougat, the BT will work initially, but not retaining for a few reboots or on/off BT setting.
If any one of you have root your device, would you please share the content (even with mask) of
/nvdata
All my files there are empty, and this would be the major cause of BT issue. I guess.
A work around or fix.
/nvdata/MACBT
you just put a mac address there in the format XX:XX:XX:XX:XX:XX
And it will be recorded and still valid after update.
I'm not able to play videos on google without it glitching out, I just think it's an open GL error but im not rly sure, does someone knows about this?
Process: com.spotify.music
Flags: 0x38d83e44
Package: com.spotify.music v85204766 (8.7.18.1138)
Foreground: Yes
Build: 'BLU/xxx/xxx:7.1.2/xxxx/xxx:userdebug/release-keys'
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Cardinal-AOSP Version: '4.5'
Build fingerprint: 'BLU/xxx/xxx:7.1.2/xxxx/xxx:userdebug/release-keys'
Revision: '0'
ABI: 'arm'
pid: 5099, tid: 5220, name: RenderThread >>> com.spotify.music <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
Abort message: 'GL errors! frameworks/base/libs/hwui/renderthread/CanvasContext.cpp:550'
r0 00000000 r1 00001464 r2 00000006 r3 00000008
r4 8f5f0978 r5 00000006 r6 8f5f0920 r7 0000010c
r8 94ae0b80 r9 00000000 sl 973882fc fp 973882f8
ip 00000000 sp 8f5eff38 lr b4384ec7 pc b4387748 cpsr 20070010
backtrace:
#00 pc 0004a748 /system/lib/libc.so (tgkill+12)
#01 pc 00047ec3 /system/lib/libc.so (pthread_kill+34)
#02 pc 0001d6f5 /system/lib/libc.so (raise+10)
#03 pc 00019241 /system/lib/libc.so (__libc_android_abort+34)
#04 pc 000171f8 /system/lib/libc.so (abort+4)
#05 pc 0000c1dd /system/lib/libcutils.so (__android_log_assert+112)
#06 pc 00024077 /system/lib/libhwui.so
#07 pc 00025a73 /system/lib/libhwui.so
#08 pc 00029035 /system/lib/libhwui.so (_ZN7android10uirenderer12renderthread12RenderThread10threadLoopEv+80)
#09 pc 0000e3fd /system/lib/libutils.so (_ZN7android6Thread11_threadLoopEPv+140)
#10 pc 00066c11 /system/lib/libandroid_runtime.so (_ZN7android14AndroidRuntime15javaThreadShellEPv+80)
#11 pc 00047993 /system/lib/libc.so (_ZL15__pthread_startPv+22)
#12 pc 00019c8d /system/lib/libc.so (__start_thread+6)