-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] crash in libCHipcontroller.so #29061
Comments
@netscell |
some app log : 09-05 14:57:27.187 14428 14646 F e:communication: runtime.cc:695] Runtime aborting... |
The libCHIPController.so file is required to accurately analyze the dump log. |
It is difficult to determine the exact situation as there is no full log for the previous situation, but it is believed that an exception occurred in the code below. reason : connectedhomeip/examples/android/CHIPTool/app/src/main/java/com/google/chip/chiptool/ChipClient.kt Line 85 in ecba41d
connectedhomeip/examples/android/CHIPTool/app/src/main/java/com/google/chip/chiptool/ChipClient.kt Line 106 in ecba41d
To prevent this, it seems that exception handling should be added on the calling side, but it is necessary to review whether this approach is correct. |
no use android chiptool application; |
@netscell is this still issue? have you tried the suggestion from @joonhaengHeo ? thanks |
also encouter the same error log: |
@netscell same here. I have attached the complete logs below.
@yunhanw-google I am already using the approach mentioned by @joonhaengHeo. Logs |
Reproduction steps
android app encouters this crash sometimes:
android crash log:
PID: 18374
UID: 10239
Frozen: false
Flags: 0x20c83e46
Foreground: No
Process-Runtime: 439568
Lifetime: 439s
Loading-Progress: 1.0
Wakefulness: Awake 2023-09-04 18:16:31.611
KeyguardShowing: false 2023-09-04 18:16:32.464
Dropped-Count: 0
Revision: '0'
ABI: 'arm64'
Timestamp: 2023-09-04 18:19:09.155291074+0800
Process uptime: 300s
pid: 18374, tid: 19037, name: CHIP Device Con
uid: 10239
tagged_addr_ctrl: 0000000000000001 (PR_TAGGED_ADDR_ENABLE)
pac_enabled_keys: 000000000000000f (PR_PAC_APIAKEY, PR_PAC_APIBKEY, PR_PAC_APDAKEY, PR_PAC_APDBKEY)
signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
Abort message: 'JNI DETECTED ERROR IN APPLICATION: mid == null
in call to NewObjectV'
x0 0000000000000000 x1 0000000000004a5d x2 0000000000000006 x3 000000712eeba180
x4 ff6d6e6873606268 x5 ff6d6e6873606268 x6 ff6d6e6873606268 x7 7f7f7f7f7f7f7f7f
x8 00000000000000f0 x9 00000074022bb398 x10 0000000000000001 x11 00000074022fb5b8
x12 00000000000050fe x13 ffffffffffffffff x14 ff00000000000000 x15 ffffffffffffffff
x16 000000740235ff88 x17 000000740233d450 x18 000000712a8c2000 x19 00000000000047c6
x20 0000000000004a5d x21 00000000ffffffff x22 0000000000000000 x23 000000712eeba3b8
x24 0000000000000000 x25 000000712eeba3b0 x26 000000712eebb000 x27 0000007141a16000
x28 000000714180b418 x29 000000712eeba200
lr 00000074022ed044 sp 000000712eeba160 pc 00000074022ed070 pst 0000000000001000
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.
NOTE: On this device, run setenforce 0 to make the libraries readable.
NOTE: Unreadable libraries:
NOTE: /lib/arm64-v8a/libCHIPController.so
#00 pc 0000000000054070 /apex/com.android.runtime/lib64/bionic/libc.so (abort+164) (BuildId: 25eadd32a5b6753e7e58e01ae8014530)
#1 pc 0000000000616b9c /apex/com.android.art/lib64/libart.so (art::Runtime::Abort(char const*)+1248) (BuildId: d53f2ad8deb01876e35b599a414617a1)
#2 pc 0000000000016ea8 /apex/com.android.art/lib64/libbase.so (android::base::SetAborter(std::__1::function<void (char const*)>&&)::$_3::__invoke(char const*)+80) (BuildId: 5965f2954d5067bd4a154d2af88c3f5b)
#3 pc 0000000000016450 /apex/com.android.art/lib64/libbase.so (android::base::LogMessage::~LogMessage()+352) (BuildId: 5965f2954d5067bd4a154d2af88c3f5b)
#4 pc 0000000000453004 /apex/com.android.art/lib64/libart.so (art::JavaVMExt::JniAbort(char const*, char const*)+2360) (BuildId: d53f2ad8deb01876e35b599a414617a1)
#5 pc 00000000004c80b4 /apex/com.android.art/lib64/libart.so (art::JNI::NewObjectV(_JNIEnv*, _jclass*, _jmethodID*, std::__va_list)+860) (BuildId: d53f2ad8deb01876e35b599a414617a1)
#6 pc 00000000002d26f0 /lib/arm64-v8a/libCHIPController.so
#7 pc 00000000002d6704 /lib/arm64-v8a/libCHIPController.so
#8 pc 00000000002d1fc4 /lib/arm64-v8a/libCHIPController.so
#9 pc 00000000008fee6c /lib/arm64-v8a/libCHIPController.so
#10 pc 00000000008fead4 /lib/arm64-v8a/libCHIPController.so
#11 pc 00000000008fefb0 /lib/arm64-v8a/libCHIPController.so
#12 pc 00000000009bffd8 /lib/arm64-v8a/libCHIPController.so
#13 pc 00000000009b67cc /lib/arm64-v8a/libCHIPController.so
#14 pc 000000000091a2cc /lib/arm64-v8a/libCHIPController.so
#15 pc 00000000009207c4 /lib/arm64-v8a/libCHIPController.so
#16 pc 000000000099a780 /lib/arm64-v8a/libCHIPController.so
#17 pc 00000000002dcfa8 /lib/arm64-v8a/libCHIPController.so
#18 pc 00000000000b8b98 /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+208) (BuildId: 25eadd32a5b6753e7e58e01ae8014530)
#19 pc 0000000000055794 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 25eadd32a5b6753e7e58e01ae8014530)
Bug prevalence
3-7times a week
GitHub hash of the SDK that was being used
sdk version 1.0.0.2
Platform
android
Platform Version(s)
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: