S9/S9 +特定的WebView设备崩溃报告 [英] S9/S9+ specific WebView device crash report

查看:411
本文介绍了S9/S9 +特定的WebView设备崩溃报告的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们一直在看到Google Play出现的崩溃报告,这些崩溃报告专门针对三星S9(starqlesq)&都运行Android 8.0.0的S9 +(star2qlesq):

We have been seeing crash reports coming into Google Play which are specific to the Samsung S9 (starqlesq) & S9+ (star2qlesq), both running Android 8.0.0:

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR) backtrace: #00 pc 0000000000a51278 /vendor/lib64/libllvm-glnext.so (_ZN13ShaderObjects17loadProgramBinaryEP15CompilerContextPvmP23QGLC_LINKPROGRAM_RESULT+1396) #01 pc 000000000099b500 /vendor/lib64/libllvm-glnext.so (_ZN15CompilerContext17loadProgramBinaryEPvmP23QGLC_LINKPROGRAM_RESULT+160) #02 pc 0000000000a6e110 /vendor/lib64/libllvm-glnext.so (_Z21QGLCLoadProgramBinaryPvS_mP23QGLC_LINKPROGRAM_RESULT+88) #03 pc 00000000001a501c /vendor/lib64/egl/libGLESv2_adreno.so (_ZN17EsxShaderCompiler21LoadProgramBinaryBlobEP10EsxContextP10EsxProgramPKvmP10EsxInfoLog+256)

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR) backtrace: #00 pc 0000000000a51278 /vendor/lib64/libllvm-glnext.so (_ZN13ShaderObjects17loadProgramBinaryEP15CompilerContextPvmP23QGLC_LINKPROGRAM_RESULT+1396) #01 pc 000000000099b500 /vendor/lib64/libllvm-glnext.so (_ZN15CompilerContext17loadProgramBinaryEPvmP23QGLC_LINKPROGRAM_RESULT+160) #02 pc 0000000000a6e110 /vendor/lib64/libllvm-glnext.so (_Z21QGLCLoadProgramBinaryPvS_mP23QGLC_LINKPROGRAM_RESULT+88) #03 pc 00000000001a501c /vendor/lib64/egl/libGLESv2_adreno.so (_ZN17EsxShaderCompiler21LoadProgramBinaryBlobEP10EsxContextP10EsxProgramPKvmP10EsxInfoLog+256)

看看上面的堆栈跟踪,崩溃似乎是在OpenGL系统代码中.

Looking at the above stack trace, the crash appears to be in OpenGL system code.

这很奇怪,因为我们集成了崩溃报告解决方案(Microsoft App Center SDK),而其他崩溃报告都将发送到App Center.

This is strange, because we have a crash reporting solution integrated (the Microsoft App Center SDK) and other crash reports are going to App Center.

我们的应用大量使用了WebView,据我所知,它现在在单独的进程中运行.

Our app makes heavy use of WebView, which I understand now uses Chrome, running in a separate process.

因此,我的问题是:

  • 此崩溃报告是否要发送到Google Play,而不是App Center指示与WebView相关的崩溃?
  • 什么样的事情会导致类似的崩溃?到目前为止,它影响了3个唯一用户,因此它似乎并不是特定于具有异常设备配置的单个用户的.
  • 缩小范围和解决问题最有效的措施是什么?
  • Is the fact this crash report is going to Google Play and not App Center indicative of a WebView related crash?
  • What sort of thing can cause a crash like this? So far it is affecting 3 unique users, so it doesn't appear to be specific to an individual user with an unusual device configuration.
  • What actions would be most effective in narrowing down and resolving the issue?

推荐答案

在这些有问题的设备上,已确认禁用硬件加速可以解决该问题:

Disabling hardware acceleration has now been confirmed as working around the issue on these problematic devices:

val product = Build.PRODUCT
val s9ProductsThatNeedWorkaround = arrayOf("starqltesq", "star2qltesq", "starqlteue", "star2qlteue")
if (s9ProductsThatNeedWorkaround.contains(product)) {
    WebView.setLayerType(LAYER_TYPE_SOFTWARE)
}

但是在租借Web内容时可能会出现一些外观异常.

There may be some cosmetic anomalies when rending web content however.

这篇关于S9/S9 +特定的WebView设备崩溃报告的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆