首页
学习
活动
专区
圈层
工具
发布
社区首页 >问答首页 >在升级到目标29之后,android 10 /apex/com.android.run/lib64/libart.so (art::OatFileManager::DumpForSigQuit )上发生了很多崩溃

在升级到目标29之后,android 10 /apex/com.android.run/lib64/libart.so (art::OatFileManager::DumpForSigQuit )上发生了很多崩溃
EN

Stack Overflow用户
提问于 2020-09-22 17:41:38
回答 1查看 2.8K关注 0票数 6

将目标sdk版本升级到29版本后,android 10的崩溃次数太多了:

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

build.gradle紧随其后

代码语言:javascript
复制
implementation 'com.android.installreferrer:installreferrer:2.1'
implementation "com.google.android.gms:play-services-base:17.4.0"
implementation "com.google.android.gms:play-services-gcm:17.0.0"
implementation "com.google.android.gms:play-services-ads:19.3.0"
implementation "com.google.android.gms:play-services-auth:18.1.0"
implementation "com.google.android.gms:play-services-location:17.0.0"
implementation "com.google.firebase:firebase-core:17.5.0"
implementation "com.google.firebase:firebase-messaging:20.2.4"
implementation "com.google.firebase:firebase-config:19.2.0"
implementation 'com.google.firebase:firebase-auth:19.3.2'
implementation 'com.google.firebase:firebase-crashlytics:17.2.1'
implementation "com.facebook.android:facebook-login:5.15.3"
implementation "com.facebook.android:facebook-messenger:5.15.3"
implementation 'com.facebook.android:audience-network-sdk:5.8.0'

看到类似问题的人知道发生了什么吗?

EN

回答 1

Stack Overflow用户

发布于 2020-10-13 21:29:41

更新audience-network-sdk至6.1.0版本可修复该bug。使用固件10上的某些设备进行了测试

票数 3
EN
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接:

https://stackoverflow.com/questions/64007059

复制
相关文章

相似问题

领券
问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档