Firebase-android-sdk: pc 00000000000830f0 /apex/com.android.runtime/lib64/bionic/libc.so (abort+160)

[viviant1224]

Issuse info

When I replaced fabric crash with firebase, the following error message occurred：

Environment

• Firebase Component:
  com.google.firebase:firebase-core:17.4.3
  com.google.firebase:firebase-crashlytics:17.2.1
  com.google.firebase:firebase-crashlytics-ndk:17.2.1
  com.google.firebase:firebase-analytics:17.5.0
  com.facebook.android:facebook-android-sdk :4.24
• Component version: Android10
  
  
  
  • targetSDKVersion: 29
  
  

The problem

---

backtrace:
#00 pc 00000000000830f0 /apex/com.android.runtime/lib64/bionic/libc.so (abort+160)
#00 pc 00000000004b81d0 /apex/com.android.runtime/lib64/libart.so (art::Runtime::Abort(char const)+2280)
#00 pc 000000000000b458 /system/lib64/libbase.so (android::base::LogMessage::~LogMessage()+580)
#00 pc 0000000000445104 /apex/com.android.runtime/lib64/libart.so (art::OatHeader::GetCompilerFilter() const+280)
#00 pc 000000000044ca2c /apex/com.android.runtime/lib64/libart.so (art::OatFile::GetCompilerFilter() const+40)
#00 pc 0000000000458130 /apex/com.android.runtime/lib64/libart.so (art::OatFileManager::DumpForSigQuit(std::__1::basic_ostream>&)+392)
#00 pc 00000000004c5590 /apex/com.android.runtime/lib64/libart.so (art::Runtime::DumpForSigQuit(std::__1::basic_ostream>&)+104)
#00 pc 00000000004d9a28 /apex/com.android.runtime/lib64/libart.so (art::SignalCatcher::HandleSigQuit()+1352)
#00 pc 00000000004d8ad4 /apex/com.android.runtime/lib64/libart.so (art::SignalCatcher::Run(void)+252)
#00 pc 00000000000e6890 /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+36)
#00 pc 0000000000084b6c /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64)

How to resolved it:

I can't reoccur it.

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[palexs]

Observing the same issue.

[mrwillis21]

Hi @viviant1224 and @palexs - are you observing this issue in your Crashlytics dashboard?

[viviant1224]

Hi @viviant1224 and @palexs - are you observing this issue in your Crashlytics dashboard?
@mrwillis21
I found this crash in the Google Play console， and the crash of libc.so reported on firebase.
I don’t know if the problem is caused by the Firebase Crash SDK.
But after I upgraded the targetSDK to 29 and replaced the fabric crash sdk with firebase crashsdk, the problem occurred.

[palexs]

@mrwillis21 Yes, I see it in Crashlytics dashboard. We've just migrated from Fabric and used the latest Firebase package:
"@react-native-firebase/crashlytics": "8.4.9". Samsung devices are most vulnerable to this issue (probably due to popularity), spread evenly between Android OS versions: 10, 9, 8 and 5.

libc.so crash:

Crashed: Thread :  SIGSEGV  0x000000000000000d
#00 pc 0x7d77b9a908 libjsc.so 
#01 pc 0x7d77c364b8 libjsc.so 
#02 pc 0x7d78265dfd libjsc.so 
#03 pc 0x7d78262350 libjsc.so 
#04 pc 0x7d77c79ea0 libjsc.so 
#05 pc 0x7d77c72068 libjsc.so 
#06 pc 0x7d77d0cc64 libjsc.so