CODEWITHSUNDEEP
androidandroid-10.0
AndroidDev
AndroidDev

Reputation: 1625

/apex/com.android.runtime/lib64/bionic/libc.so (abort+160), abort crash in Android 10 devices

I recently changed targedtSdk to 29 and made a release. And started getting this crash called abort. Below is the stack trace that I got from play console. All the crashes are happening only in Android 10 devices. Apart from these, there is no other info.

   #00  pc 0000000000082fb4  /apex/com.android.runtime/lib64/bionic/libc.so (abort+160)
   #00  pc 00000000004b4888  /apex/com.android.runtime/lib64/libart.so (art::Runtime::Abort(char const*)+2268)
   #00  pc 000000000000c5b4  /system/lib64/libbase.so (android::base::LogMessage::~LogMessage()+608)
   #00  pc 0000000000442f8c  /apex/com.android.runtime/lib64/libart.so (art::OatHeader::GetCompilerFilter() const+280)
   #00  pc 000000000044a884  /apex/com.android.runtime/lib64/libart.so (art::OatFile::GetCompilerFilter() const+40)
   #00  pc 0000000000455d38  /apex/com.android.runtime/lib64/libart.so (art::OatFileManager::DumpForSigQuit(std::__1::basic_ostream<char, std::__1::char_traits<char>>&)+376)
   #00  pc 00000000004c1d78  /apex/com.android.runtime/lib64/libart.so (art::Runtime::DumpForSigQuit(std::__1::basic_ostream<char, std::__1::char_traits<char>>&)+104)
   #00  pc 00000000004d5ad8  /apex/com.android.runtime/lib64/libart.so (art::SignalCatcher::HandleSigQuit()+1356)
   #00  pc 00000000004d4b6c  /apex/com.android.runtime/lib64/libart.so (art::SignalCatcher::Run(void*)+252)
   #00  pc 00000000000e205c  /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+36)
   #00  pc 0000000000084af0  /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64)```


Made a staged rollout of 50% and the number of crashes for above is around 800 per day with active installs of 1.5M. So this is a major issue.

Upvotes: 33

Views: 31903

Answers (4)

groxo
groxo

Reputation: 31

I did not use com.facebook.android:audience-network-sdk, and have been trying to fix this for a week now. After much research on the web (and finding nothing of use), I decided to bet it was some sort of incompatibility between some lib and the Andriod version. Took the libs out one by one, and found that, in my case at least, the problem was Sentry. Simply not invoking it during app start solved the issue.

Upvotes: 3

Lin Lin
Lin Lin

Reputation: 259

enter image description hereAudience Network SDK 6.2.0 seems to solve the problem

https://developers.facebook.com/docs/audience-network/changelog-android#6_2_0

Upvotes: 1

David Santiago Turi&#241;o
David Santiago Turi&#241;o

Reputation: 1136

As per https://issuetracker.google.com/issues/148240970#comment8 it looks like something to be fixed for Android 11 onwards, without a known fix for Android 10.

Upvotes: 1

yukun qian
yukun qian

Reputation: 81

I fixed this bug， from implementation 'com.facebook.android:audience-network-sdk:5.11.0' to implementation 'com.facebook.android:audience-network-sdk:5.4.1'

But can't find the reason

Upvotes: 2

Related Questions