I am using the jitsi_meet_wrapper plugin in my flutter app, and the release apk crashes every time when I click the join meeting button. However, the app runs perfectly fine in emulator after the first run. In the first run(which I do just after flutter clean and then flutter run), the log files of the crash are these
F/libc (20680): Fatal signal 4 (SIGILL), code 1 (ILL_ILLOPC), fault addr 0x7c4913d320 in tid 20780 (mqt_js), pid 20680 (ik.coachingtime)
Build fingerprint: 'google/sdk_gphone64_arm64/emulator64_arm64:10/QSR1.217802.001/7690624:user/release-keys'
Revision: '0'
ABI: 'arm64'
Timestamp: 2023-02-18 20:23:52+0530
pid: 20680, tid: 20780, name: mqt_js >>> in.novik.coachingtime <<<
uid: 10150
signal 4 (SIGILL), code 1 (ILL_ILLOPC), fault addr 0x7c4913d320 (*pc=0xd3407c21)
x0 0000007c485426dc x1 0000000000000000 x2 0000000000000020 x3 0000000000000000
x4 0000000000000000 x5 0000000000000000 x6 17fffff454fff4a9 x7 5280000192800000
x8 0000007c4913d320 x9 0000000000002000 x10 000000000000000c x11 000000000007c486
x12 0000000000000005 x13 0000007c48500000 x14 000000006e731ebf x15 0000000000000001
x16 0000007c5b6213d8 x17 0000007d85f438c0 x18 0000007c542ba000 x19 0000007c457218c0
x20 0000000000000000 x21 0000007c54558368 x22 0000007c48f00000 x23 0000007c457218e0
x24 0000000000000000 x25 0000007c45237790 x26 0000007c457218c0 x27 0000007c48f0ccc8
x28 ffff000000000002 x29 0000007c54558400
sp 0000007c54558290 lr 0000007c5b2eb844 pc 0000007c4913d320
backtrace:
NOTE: Function names and BuildId information is missing for some frames due
NOTE: to unreadable libraries. For unwinds of apps, only shared libraries
NOTE: found under the lib/ directory are readable.
#00 pc 000000000003e320 <anonymous:7c490ff000>
#01 pc 0000000000557840 /data/data/in.novik.coachingtime/lib-main/libjsc.so
#02 pc 0000000000563414 /data/data/in.novik.coachingtime/lib-main/libjsc.so
#03 pc 0000000000566788 /data/data/in.novik.coachingtime/lib-main/libjsc.so
#04 pc 00000000000001ec <anonymous:7c490ff000>
Lost connection to device.
Related
The application builds without any issues but when it is installed on the real Pixel devices it crashed on start.
From the Google Play console, I see the error in pre-launch reports with this stack trace:
Signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
Abort message: 'Pointer tag for 0x79a03e8170 was truncated.'
x0 0000000000000000 x1 000000000000594c x2 0000000000000006 x3 00000078fd5da880
x4 0000000000000000 x5 0000000000000000 x6 0000000000000000 x7 0000000000000020
x8 00000000000000f0 x9 0000007c142be7c0 x10 ffffff80fffffbdf x11 0000000000000001
x12 0000000000000018 x13 0000000000000003 x14 0000000000000065 x15 00000078fd5da2b2
x16 0000007c14356c80 x17 0000007c14338320 x18 00000078fd0fe000 x19 00000000000058f2
x20 000000000000594c x21 00000000ffffffff x22 00000078fd5da9c0 x23 0000000000000000
x24 0000000000000099 x25 00000000000000a5 x26 00000079013521e2 x27 0000007901354010
x28 0000007901354000 x29 00000078fd5da900
lr 0000007c142ec148 sp 00000078fd5da860 pc 0000007c142ec178 pst 0000000000001000
I can see the same issue using the logcat with the connected real device to the laptop. On the emulator, it is not reproducible.
Before this error, it was another one with okhttp3 but it was fixed by adding the following code to the android/build/build.gradle:
implementation("com.squareup.okhttp3:okhttp:4.9.2")
implementation("com.squareup.okhttp3:okhttp-urlconnection:4.9.2")
React Native version is: "react-native": "0.63.3"
Any idea what this might be related to?
I've released a simple mobile game for android using unity. However, if you uninstall and reinstall the app from the play store the game crashes every time you try to open it until you clear cache/data. This is not reproducible from development builds, it only occurs with the version that is downloaded from the Play Store.
Details:
Unity 2019.1.13f1,
Android.
The Error message I get from google developer console:
java.lang.Error: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0000000000000010 Build fingerprint: 'HUAWEI/ELE-L29EEA/HWELE:9/HUAWEIELE-L29/9.1.0.193C431:user/release-keys' Revision: '0' pid: 25899, tid: 25924, name: UnityMain >>> com.UCSsoftware.ColorDrop <<< x0 0000007299f7d610 x1 0000007286559fa0 x2 000000000000010f x3 0000000000000001 x4 0000000000000000 x5 0000000000000000 x6 000000732a7f8000 x7 0000000003dc3ba8 x8 0000000000000000 x9 0000000000000000 x10 0000007283f6b000 x11 0000000000002e1f x12 ffffffffffff8000 x13 ffffffffa260f39e x14 000000000507d7d6 x15 0000007286408cc8 x16 00000073269301a0 x17 00000073268c5524 x18 0000007286408068 x19 000000000000000b x20 0000000000000060 x21 00000072840ee470 x22 000000000000005c x23 00000072855a1000 x24 00000072855a1000 x25 0000007299f20d70 x26 0000000000000002 x27 000000728411ca30 x28 0000000000000000 x29 0000007287784e90 x30 0000007284dfbab0 sp 0000007287784e10 pc 0000007284dfba68 pstate 0000000080000000 at [vdso].(
at split_config. (0)
at split_config. (0)
at split_config. (0)
at split_config. (0)
at split_config. (0)
at split_config. (0)
at split_config. (0)
at base. (0)
It's a bug that has been fixed in unity 2019.2.6f1.
You can find more information here.
Recently I've got all users of Samsung Galaxy S7 complaining that app crashes instantly upon start. I didn't get any crash logs from Crashlytics about this issue which was strange at least. But luckily some users reported the issues to Play Store and I was able to get at least some info.
So here's the log from Play Store dev console:
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'samsung/hero2ltexx/hero2lte:6.0.1/MMB29K/G935FXXU1APF2:user/release-keys'
Revision: '9'
ABI: 'arm64'
pid: 18857, tid: 18900, name: GLThread 12749 >>> com.some.package <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x6b260
x0 0000007fb17836c0 x1 0000007fb1783788 x2 0000000000000001 x3 0000000000000001
x4 0000000000000000 x5 0000007f981afe50 x6 0000000000000000 x7 0000000000000000
x8 0000000000000001 x9 0000007f9993a570 x10 0000000000000001 x11 0000000000000036
x12 0000000000000001 x13 0000000000000000 x14 0000007f9a8ed000 x15 0000000000000000
x16 0000007fa50afa40 x17 0000000000000000 x18 0000000000570000 x19 0000000000000000
x20 000000000006b000 x21 0000000000000000 x22 0000007f981791c0 x23 0000000000000000
x24 0000007fb17836c0 x25 0000007f9a8dc000 x26 0000007f981afd60 x27 0000000000000001
x28 0000000000000000 x29 0000007f99939db0 x30 0000007fa3d50d74
sp 0000007f99939d10 pc 0000007fa3d50bfc pstate 0000000060000000
backtrace:
#00 pc 0000000000645bfc /system/vendor/lib64/egl/libGLES_mali.so (eglp_swap_buffers+248)
#01 pc 000000000002cf6c /system/lib64/libEGL.so (eglSwapBuffersWithDamageKHR+560)
#02 pc 000000000009a5b8 /system/lib64/libandroid_runtime.so
#03 pc 0000000003f17ad4 /system/framework/arm64/boot.oat (offset 0x2f34000)
This makes me think that the issue is a firmware problem because:
occurs only on S7 Edge (although once it happenned on plain S7)
last 4 lines of the stack trace point on EGL system libs
So my questions would be:
Is it possible to find out which part of app code makes calls that trigger the issue?
Has anybody got the same/similar issue and fixed it?
Thanks ahead!
try set final modify with data render
final FloatBuffer tmpfbXYZ = actor.fbXYZ
glDrawArrays(GL_TRIANGLES,0, tmpfbXYZ);
My app is crashing for all Android Marshmallow arm64 devices on startup. Users were previously using the app on Lollipop on the same device, but then started reporting these crashes after their devices were updated to Marshmallow. 32-bit devices are not affected. The crash reports all look like this:
ABI: 'arm64'
pid: 3531, tid: 3531, name: ompany.myapp >>> com.mycompany.myapp <<<
signal 4 (SIGILL), code 1 (ILL_ILLOPC), fault addr 0x7f796d9370
x0 0000000013087000 x1 0000007f8815da00 x2 0000000000000002 x3 0000000000000004
x4 b42e90dfe44ab496 x5 b42e90dfe44ab496 x6 0000000000000000 x7 00000000019b7af0
x8 0000000013087000 x9 0000007f87713000 x10 0000000000000601 x11 000000001308700c
x12 0000000000002000 x13 0000000000002000 x14 000000006fb18428 x15 00000000013cd010
x16 0000000000000000 x17 0000000000002000 x18 0000005594f27e90 x19 0000000000000003
x20 0000000013087000 x21 0000007f75e00098 x22 00000000130d6e20 x23 0000000000000601
x24 0000000000000000 x25 0000000000000001 x26 0000000000000000 x27 0000000000000000
x28 0000000000000000 x29 00000000130d6e20 x30 0000007f796d9350
sp 0000007ff8a7bc60 pc 0000007f796d9370 pstate 0000000080000000
backtrace:
#00 pc 0000000000929370 /data/app/com.mycompany.myapp-1/oat/arm64/base.odex (offset 0x486000)
#01 pc 000000000092934c /data/app/com.mycompany.myapp-1/oat/arm64/base.odex (offset 0x486000)
The offset 0x486000 is consistent across all reports.
Can I use this offset to debug the crash? Some more info about the app:
There is no native code (it's all Java)
If I unzip the apk, the directory looks like this (there is no lib directory)
[res], [assets], [META-INF], classes.dex, resources.arsc, AndroidManifest.xml
I've read about the abi filtering tricks that some people are using the exclude arm64 libs from their builds,forcing the system to load the 32bit libs, but I have no native code and no libs directory.
My guess is that there's something I can do with that offset, but I'm not sure where to start.
My app was crashing in arm64 devices (Nexus 9). I tried this answer and it helped me. Now its running on all devices i have tested so far.
I had a production APK in the Play store, which was using a third party native library. I had 3 architectures in the jniLibs directory, namely armeabi, armeabi-v7a and x86.
I recently updated the build and removed the library using the native code (as I don't need that anymore). However, to my surprise, I observed random crashes on 64 bit devices, immediately after updating the application.
Following are the primary devices affected:
All 64 bit devices running Android 6.0 (Marshmallow) - Nexus 5X, Nexus
6P, HTC One M9, LG G4, Moto X Pure Edition
Samsung Galaxy S6 series running Android 5.1 (Lollipop)
And here is the crash trace on Android 6.0:
Build fingerprint: 'htc/himauhl_htc_europe/htc_himauhl:6.0/MRA58K/671758.12:user/release-keys'
Revision: '0'
ABI: 'arm64'
pid: 23807, tid: 23971, name: Chrome_InProcGp >>> com.my.app <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x5594d38d40
x0 0000005594534d40 x1 0000005594535710 x2 0000000000000000 x3 0000000000002460
x4 00000055945371a0 x5 0000000000804000 x6 0000000000000000 x7 0000007f3ff19e58
x8 0000000000000000 x9 0000005594534db0 x10 0000008400804000 x11 0000000000804000
x12 0000005594d38d40 x13 0000000000000130 x14 0000000000000000 x15 00000000000009d0
x16 0000007f750f34a8 x17 0000007f74d386e4 x18 0000007f3ff19e58 x19 0000000000000a48
x20 0000005593d7eaa0 x21 0000000000000001 x22 0000005594534d40 x23 0000000000000001
x24 0000000000000000 x25 00000000000007b4 x26 00000000000009d0 x27 0000007f74f1ecb8
x28 0000005594535710 x29 0000007f3ff19ab0 x30 0000007f74d38de0
sp 0000007f3ff19aa0 pc 0000007f74d38734 pstate 0000000060000000
backtrace:
#00 pc 0000000000cef734 /system/vendor/lib64/libllvm-glnext.so (ShaderObjects::adjustSymbolPointers(char*, GLSL_SYMBOL*)+80)
#01 pc 0000000000cefddc /system/vendor/lib64/libllvm-glnext.so (ShaderObjects::loadProgramBinary(CompilerContext*, void*, unsigned long, QGLC_LINKPROGRAM_RESULT*)+812)
#02 pc 0000000000c71e3c /system/vendor/lib64/libllvm-glnext.so (CompilerContext::loadProgramBinary(void*, unsigned long, QGLC_LINKPROGRAM_RESULT*)+176)
#03 pc 0000000000d05868 /system/vendor/lib64/libllvm-glnext.so (QGLCLoadProgramBinary(void*, void*, unsigned long, QGLC_LINKPROGRAM_RESULT*)+68)
#04 pc 00000000001a4af0 /system/vendor/lib64/egl/libGLESv2_adreno.so (EsxShaderCompiler::LoadProgramBinaryBlob(EsxContext*, EsxProgram*, void const*, unsigned long, EsxInfoLog*)+144)
#05 pc 000000000018d104 /system/vendor/lib64/egl/libGLESv2_adreno.so (EsxProgram::LoadProgramBinary(EsxContext*, unsigned int, void const*, int)+164)
#06 pc 000000000012e608 /system/vendor/lib64/egl/libGLESv2_adreno.so (EsxContext::GlProgramBinary(unsigned int, unsigned int, void const*, int)+136)
#07 pc 0000000000111a44 /system/vendor/lib64/egl/libGLESv2_adreno.so (glProgramBinary+68)
#08 pc 00000000008372b4 /data/app/com.google.android.webview-1/lib/arm64/libwebviewchromium.so
And here is the crash trace on Samsung S6 devices (Android 5.1)
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'samsung/zerofltexx/zeroflte:5.1.1/LMY47X/G920FXXU3COI9:user/release-keys'
Revision: '11'
ABI: 'arm64'
pid: 19133, tid: 19323, name: AsyncTask #8 >>> com.my.app <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x1c
x0 0000000033441be0 x1 0000000000668837 x2 0000000000000068 x3 0000000000000006
x4 0000000032d694c0 x5 0000000002cf95e0 x6 0000000033441be0 x7 0000007f831c8800
x8 00000000711c5508 x9 0000000000000000 x10 0000000033441be0 x11 0000007f831c8610
x12 0000000000000002 x13 00000000033263c0 x14 0000000002cf95e0 x15 0000000033441008
x16 000000003fffffff x17 000000000000005d x18 0000007f2fcaf000 x19 000000000000005f
x20 0000000033441be0 x21 0000000000000000 x22 0000000000000003 x23 0000000033441ac0
x24 000000008a00af80 x25 0000000033441ba0 x26 0000000033441b20 x27 0000000033441b40
x28 0000000033441b60 x29 0000000000000001 x30 0000007f72beb9ac
sp 0000007f623ff450 pc 0000007f72beb9b0 pstate 0000000020000000
backtrace:
#00 pc 00000000002e89b0 /data/dalvik-cache/arm64/data#app#com.my.app-2#base.apk#classes.dex
#01 pc 00000000002e89a8 /data/dalvik-cache/arm64/data#app#com.my.app-2#base.apk#classes.dex
What could be the issue and how to rectify this?