[Bug]: unwindstack::SignalHandler(int, siginfo*, void*)

[laraibsaghir0]

What happened?

Alot of ANRs are being logged in Firebase Analytics after upgrading to one signal version 5.4.0.

Steps to reproduce?

Many users face ANR when the app runs. There are no specific steps to reproduce this issue.

What did you expect to happen?

No ANR in my app.

OneSignal Android SDK version

5.4.0

Android version

15

Specific Android models

Nothing Phone (3a)

Relevant log output

com.mynayatel (native):tid=29510 systid=29510 
#00 pc 0x9155c libunwindstack.so (unwindstack::SignalHandler(int, siginfo*, void*)) (BuildId: b8ba3194446b11b35b94590413c5fced)
#01 pc 0x860 [vdso]
#02 pc 0xc6608 libc.so (__epoll_pwait + 8) (BuildId: f98650a65aa2ec2d87236752af90aa7e)
#03 pc 0x13cc8 libutils.so (android::Looper::pollInner(int) + 196) (BuildId: 7898b82fed0acaf692cff1dba07b2a3c)
#04 pc 0x13ba0 libutils.so (android::Looper::pollOnce(int, int*, int*, void**) + 124) (BuildId: 7898b82fed0acaf692cff1dba07b2a3c)
#05 pc 0x192a14 libandroid_runtime.so (android::android_os_MessageQueue_nativePollOnce(_JNIEnv*, _jobject*, long, int) + 48) (BuildId: 0dd9223b5e81510be62c1c5eaefca8c5)
#06 pc 0xd4af00 boot.oat (art_jni_trampoline + 112)
#07 pc 0x925770 boot.oat (android.os.MessageQueue.next + 256)
#08 pc 0x922628 boot.oat (android.os.Looper.loopOnce + 88)
#09 pc 0x922448 boot.oat (android.os.Looper.loop + 1112)
#10 pc 0x6c5f70 boot.oat (android.app.ActivityThread.main + 2032)
#11 pc 0x317460 libart.so (art_quick_invoke_static_stub + 640) (BuildId: eb4ec0f1d1c7267591d83fa87cb36390)
#12 pc 0x311508 libart.so (_jobject* art::InvokeMethod<(art::PointerSize)8>(art::ScopedObjectAccessAlreadyRunnable const&, _jobject*, _jobject*, _jobject*, unsigned long) + 544) (BuildId: eb4ec0f1d1c7267591d83fa87cb36390)
#13 pc 0x5c82c8 libart.so (art::Method_invoke(_JNIEnv*, _jobject*, _jobject*, _jobjectArray*) (.__uniq.165753521025965369065708152063621506277) + 32) (BuildId: eb4ec0f1d1c7267591d83fa87cb36390)
#14 pc 0xd4bfc4 boot.oat (art_jni_trampoline + 116)
#15 pc 0xc172c4 boot.oat (com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run + 116)
#16 pc 0xc216b4 boot.oat (com.android.internal.os.ZygoteInit.main + 3204)
#17 pc 0x317460 libart.so (art_quick_invoke_static_stub + 640) (BuildId: eb4ec0f1d1c7267591d83fa87cb36390)
#18 pc 0x316100 libart.so (art::JValue art::InvokeWithVarArgs<_jmethodID*>(art::ScopedObjectAccessAlreadyRunnable const&, _jobject*, _jmethodID*, std::__va_list) + 800) (BuildId: eb4ec0f1d1c7267591d83fa87cb36390)
#19 pc 0x639868 libart.so (art::JNI<true>::CallStaticVoidMethodV(_JNIEnv*, _jclass*, _jmethodID*, std::__va_list) + 156) (BuildId: eb4ec0f1d1c7267591d83fa87cb36390)
#20 pc 0xdd42c libandroid_runtime.so (_JNIEnv::CallStaticVoidMethod(_jclass*, _jmethodID*, ...) + 108) (BuildId: 0dd9223b5e81510be62c1c5eaefca8c5)
#21 pc 0xf4314 libandroid_runtime.so (android::AndroidRuntime::start(char const*, android::Vector<android::String8> const&, bool) + 916) (BuildId: 0dd9223b5e81510be62c1c5eaefca8c5)
#22 pc 0x4654 app_process64 (main + 1428) (BuildId: b46373270a3dc7e7fead6c71e2d46848)
#23 pc 0x59ac0 libc.so (__libc_init + 120) (BuildId: f98650a65aa2ec2d87236752af90aa7e)

Code of Conduct

• I agree to follow this project's Code of Conduct

[jinliu9508]

Thanks for sharing the stack trace. Based on the information provided, this crash does not appear to be related to the OneSignal SDK. We’ll go ahead and close this issue. If you discover additional logs or evidence that link the problem to OneSignal, feel free to reopen the issue and we’ll be happy to take another look.