We believe that the crash started on January 26th around the time that 121.0.6167 was released.

crash spike graph

Related WordPress/Jetpack app issue

This should be a reporting issue, not an actual regression.

The reporting of this particular issue was changed in M121, that is why it appears as a new crash. Specifically - it was previously reported as generic "native crash" with the message "please include the Java exception in the crash report". Now the actual Java exception is surfaced in the crash report, together with the obfuscated native stack trace. This implies, that you should see a corresponding decrease of those old native crashes, while the overall (total) crash rate should be roughly stable.

Can you confirm if the overall crash rate changed significantly?

The issue itself of the ResourceNotFoundException at DeviceFormFactor.isTablet (can happen in other places as well, since its caused by the resource loading mechanism) has been known for a while and the WebView team is looking into it.

Some context quoting torne@chromium.org:

The actual problem itself (WebView resources not being found, which is often but not always reported in DeviceFormFactor.isTablet or similar methods) is a longstanding issue (since at least Android 7 or earlier) with how WebView loads its resources into your app when you use it. The mechanism in the framework that WebView uses for this is, unfortunately, fragile and has bad interactions with a number of other app/library behaviours and with other OS features. Most ways for the problem to occur are timing issues between threads and very rarely affect the same user repeatedly: usually this is effectively just a tiny chance of the crash happening each time your app initializes WebView for the first time in the process, and will be more-or-less randomly distributed across your entire userbase.

We've recently made some developments in understanding some cases of this problem, as it's been happening to many apps more frequently over the last ~2 years than in the past. There's a change coming in WebView M123 (sometime in mid-March) which I'm hoping will reduce the frequency of these crashes somewhat, but we won't know how well this works for some time. There are also potentially things your app can do to reduce the frequency by being careful exactly how you initialize the WebView implementation, but it's very difficult to guess what is relevant for any particular app, and it's virtually never possible to reproduce the problem to test any changes or investigate the cause of any particular case.

One recently-relevant cause that we know about is Play dynamic feature delivery (which uses the OS's ability to install additional splits without killing the app process) - if a new feature module is installed while WebView is being initialized in the process, this can cause this crash to occur. If you do use dynamic feature modules in your app, the best way to do this is unfortunately to complete all module installations before calling any WebView APIs. Any other features that update the resource/asset configuration in your app at runtime can also cause it, and again, if you're aware of any cases where your app does something like that it's best to either avoid it entirely or do it before calling any WebView APIs. There are many, many other cases and a lot of them are not really under the app's control, so there's only limited advice we can give here.

Thank you for your response. We really appreciate this. Let us know if we can provide more information. Are there any recent changes in the Android System WebView that may have triggered the spike? If yes is there any change we should apply on how we handle the WebView to prevent the crash? We first saw this issue a few weeks ago even in old app versions that were released a year ago and now is our top crash for the recent versions of our apps.

Can you confirm if the overall crash rate changed significantly?

Looking at the data for the two crashes

• [base.apk!libmonochrome_64.so] SIGTRAP
• chromium-TrichromeWebViewGoogle6432.aab-stable-616714433 - org.chromium.ui.base.DeviceFormFactor.isTablet

the overall crash rate doesn't seem to have changed significantly (attaching the two graphs).

If the overall crash rate hasn't changed then there isn't a spike. The same crashes are happening as before, but are being reported in a more-understandable way now.

As mentioned above, this is a longstanding issue and is very difficult to investigate any particular case, and even if the specific cause is understood there is not necessarily anything you can do to avoid it. So, if your app isn't doing unusual things with resources/assets/contexts, and you aren't using Play dynamic feature delivery, or anything else that might be updating the resource configuration in your app at runtime, then there's unfortunately not really anything we can suggest.

Would like to report that we are seeing the same crash on our app https://play.google.com/store/apps/details?id=com.jio.media.ondemand

Fatal Exception: org.chromium.base.JniAndroid$UncaughtExceptionException
Native stack trace: #00 pc 0x00000000040ef587 /data/app/~~klpouyg2TP22KQ2xOpzdxA==/com.google.android.trichromelibrary_626110633-z9Hyy7MWJneBF91Mcg6c7w==/base.apk (offset 0x8dc000) #01 pc 0x0000000002c9a367 /data/app/~~klpouyg2TP22KQ2xOpzdxA==/com.google.android.trichromelibrary_626110633-z9Hyy7MWJneBF91Mcg6c7w==/base.apk (offset 0x8dc000) #02 pc 0x0000000002c9926f /data/app/~~klpouyg2TP22KQ2xOpzdxA==/com.google.android.trichromelibrary_626110633-z9Hyy7MWJneBF91Mcg6c7w==/base.apk (offset 0x8dc000) #03 pc 0x0000000003ef8923 /data/app/~~klpouyg2TP22KQ2xOpzdxA==/com.google.android.trichromelibrary_626110633-z9Hyy7MWJneBF91Mcg6c7w==/base.apk (offset 0x8dc000) #04 pc 0x0000000003f91c8f /data/app/~~klpouyg2TP22KQ2xOpzdxA==/com.google.android.trichromelibrary_626110633-z9Hyy7MWJneBF91Mcg6c7w==/base.apk (offset 0x8dc000) #05 pc 0x0000000003f91c37 /data/app/~~klpouyg2TP22KQ2xOpzdxA==/com.google.android.trichromelibrary_626110633-z9Hyy7MWJneBF91Mcg6c7w==/base.apk (offset 0x8dc000) #06 pc 0x0000000003ef9953 /data/app/~~klpouyg2TP22KQ2xOpzdxA==/com.google.android.trichromelibrary_626110633-z9Hyy7MWJneBF91Mcg6c7w==/base.apk (offset 0x8dc000) #07 pc 0x0000000003dc87a3 /data/app/~~klpouyg2TP22KQ2xOpzdxA==/com.google.android.trichromelibrary_626110633-z9Hyy7MWJneBF91Mcg6c7w==/base.apk (offset 0x8dc000) #08 pc 0x0000000003dc85ef /data/app/~~klpouyg2TP22KQ2xOpzdxA==/com.google.android.trichromelibrary_626110633-z9Hyy7MWJneBF91Mcg6c7w==/base.apk (offset 0x8dc000) #09 pc 0x00000000073ce1ab /data/app/~~klpouyg2TP22KQ2xOpzdxA==/com.google.android.trichromelibrary_626110633-z9Hyy7MWJneBF91Mcg6c7w==/base.apk (offset 0x8dc000) #10 pc 0x00000000073cf033 /data/app/~~klpouyg2TP22KQ2xOpzdxA==/com.google.android.trichromelibrary_626110633-z9Hyy7MWJneBF91Mcg6c7w==/base.apk (offset 0x8dc000) #11 pc 0x000000000648a5e7 /data/app/~~klpouyg2TP22KQ2xOpzdxA==/com.google.android.trichromelibrary_626110633-z9Hyy7MWJneBF91Mcg6c7w==/base.apk (offset 0x8dc000) #12 pc 0x000000000648a5e7 /data/app/~~klpouyg2TP22KQ2xOpzdxA==/com.google.android.trichromelibra<truncated: 1197 chars>


Caused by android.content.res.Resources$NotFoundException: Resource ID #0x20c0006
       at android.content.res.ResourcesImpl.getValue(ResourcesImpl.java:236)
       at android.content.res.Resources.getInteger(Resources.java:1192)
       at org.chromium.ui.base.DeviceFormFactor.isTablet(chromium-TrichromeWebViewGoogle6432.aab-stable-626110633:9)
       at android.os.MessageQueue.nativePollOnce(MessageQueue.java)
       at android.os.MessageQueue.next(MessageQueue.java:335)
       at android.os.Looper.loopOnce(Looper.java:169)
       at android.os.Looper.loop(Looper.java:317)
       at android.app.ActivityThread.main(ActivityThread.java:7942)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:568)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1045)

We see the same crashes - strange that this is marked won't fix given many apps are being affected by it (it's rare but our top crash right now).

There's a change coming in WebView M123 (sometime in mid-March) which I'm hoping will reduce the frequency of these crashes somewhat, but we won't know how well this works for some time.

We have added logging of the webview version that our app uses and we see that the crash persists for Webview versions >= 123

This remains our top crash. Is there a way to reopen this issue for investigation?

Would like to reopen this issue, as our crash free is going too bad in recent days.

Fatal Exception: org.chromium.base.JniAndroid$UncaughtExceptionException: Native stack trace:
#00 pc 0x0000000003e82423 /data/app/~~AeOVCbDV07-7dCjzVhm53g==/com.google.android.trichromelibrary_631209933-Jrmdo9mIBCnVtjEMS1zIFg==/base.apk (offset 0x8dc000)
#01 pc 0x0000000002cf7f23 /data/app/~~AeOVCbDV07-7dCjzVhm53g==/com.google.android.trichromelibrary_631209933-Jrmdo9mIBCnVtjEMS1zIFg==/base.apk (offset 0x8dc000)
#02 pc 0x0000000002cf8dc7 /data/app/~~AeOVCbDV07-7dCjzVhm53g==/com.google.android.trichromelibrary_631209933-Jrmdo9mIBCnVtjEMS1zIFg==/base.apk (offset 0x8dc000)
#03 pc 0x0000000003cfdd5b /data/app/~~AeOVCbDV07-7dCjzVhm53g==/com.google.android.trichromelibrary_631209933-Jrmdo9mIBCnVtjEMS1zIFg==/base.apk (offset 0x8dc000)
#04 pc 0x0000000003b60f73 /data/app/~~AeOVCbDV07-7dCjzVhm53g==/com.google.android.trichromelibrary_631209933-Jrmdo9mIBCnVtjEMS1zIFg==/base.apk (offset 0x8dc000)
#05 pc 0x0000000003b60f1b /data/app/~~AeOVCbDV07-7dCjzVhm53g==/com.google.android.trichromelibrary_631209933-Jrmdo9mIBCnVtjEMS1zIFg==/base.apk (offset 0x8dc000)
#06 pc 0x0000000003c1f777 /data/app/~~AeOVCbDV07-7dCjzVhm53g==/com.google.android.trichromelibrary_631209933-Jrmdo9mIBCnVtjEMS1zIFg==/base.apk (offset 0x8dc000)
#07 pc 0x0000000003b4ad93 /data/app/~~AeOVCbDV07-7dCjzVhm53g==/com.google.android.trichromelibrary_631209933-Jrmdo9mIBCnVtjEMS1zIFg==/base.apk (offset 0x8dc000)
#08 pc 0x0000000003b4abdf /data/app/~~AeOVCbDV07-7dCjzVhm53g==/com.google.android.trichromelibrary_631209933-Jrmdo9mIBCnVtjEMS1zIFg==/base.apk (offset 0x8dc000)
#09 pc 0x00000000072a8963 /data/app/~~AeOVCbDV07-7dCjzVhm53g==/com.google.android.trichromelibrary_631209933-Jrmdo9mIBCnVtjEMS1zIFg==/base.apk (offset 0x8dc000)
#10 pc 0x00000000072a97ef /data/app/~~AeOVCbDV07-7dCjzVhm53g==/com.google.android.trichromelibrary_631209933-Jrmdo9mIBCnVtjEMS1zIFg==/base.apk (offset 0x8dc000)
#11 pc 0x0000000006374c07 /data/app/~~AeOVCbDV07-7dCjzVhm53g==/com.google.android.trichromelibrary_631209933-Jrmdo9mIBCnVtjEMS1zIFg==/base.apk (offset 0x8dc000)
#12 pc 0x00000000074ba17b /data/app/~~AeOVCbDV07-7dCjzVhm53g==/com.google.android.trichromelibra<truncated: 778 chars>
       at org.chromium.base.JniAndroid.handleException(chromium-TrichromeWebViewGoogle6432.aab-stable-631209933:21)
       at android.os.MessageQueue.nativePollOnce(MessageQueue.java)
       at android.os.MessageQueue.next(MessageQueue.java:340)
       at android.os.Looper.loopOnce(Looper.java:168)
       at android.os.Looper.loop(Looper.java:299)
       at android.app.ActivityThread.main(ActivityThread.java:8280)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:576)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1073)


Caused by android.content.res.Resources$NotFoundException: Resource ID #0x20c0006
       at android.content.res.ResourcesImpl.getValue(ResourcesImpl.java:255)
       at android.content.res.MiuiResourcesImpl.getValue(MiuiResourcesImpl.java:96)
       at android.content.res.Resources.getInteger(Resources.java:1221)
       at org.chromium.ui.base.DeviceFormFactor.isTablet(chromium-TrichromeWebViewGoogle6432.aab-stable-631209933:9)
       at android.os.MessageQueue.nativePollOnce(MessageQueue.java)
       at android.os.MessageQueue.next(MessageQueue.java:340)
       at android.os.Looper.loopOnce(Looper.java:168)
       at android.os.Looper.loop(Looper.java:299)
       at android.app.ActivityThread.main(ActivityThread.java:8280)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:576)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1073)

we are experiencing the same issue, but seems to caused java.util.ConcurrentModificationException we have a lot of crashes in both 2 apps

Fatal Exception: org.chromium.base.JniAndroid$UncaughtExceptionException: Native stack trace:
#00 pc 0x00000000072fc7d3 /data/app/~~iqNzeqm6H35xOHwrI-bDjQ==/com.google.android.trichromelibrary_636705433-LrOgBRHApr9q42tJ7YTurQ==/base.apk (offset 0x8dc000)
#01 pc 0x0000000005f70b37 /data/app/~~iqNzeqm6H35xOHwrI-bDjQ==/com.google.android.trichromelibrary_636705433-LrOgBRHApr9q42tJ7YTurQ==/base.apk (offset 0x8dc000)
#02 pc 0x00000000027b3e8f /data/app/~~iqNzeqm6H35xOHwrI-bDjQ==/com.google.android.trichromelibrary_636705433-LrOgBRHApr9q42tJ7YTurQ==/base.apk (offset 0x8dc000)
#03 pc 0x00000000070b137f /data/app/~~iqNzeqm6H35xOHwrI-bDjQ==/com.google.android.trichromelibrary_636705433-LrOgBRHApr9q42tJ7YTurQ==/base.apk (offset 0x8dc000)
#04 pc 0x0000000005fca5bf /data/app/~~iqNzeqm6H35xOHwrI-bDjQ==/com.google.android.trichromelibrary_636705433-LrOgBRHApr9q42tJ7YTurQ==/base.apk (offset 0x8dc000)
#05 pc 0x000000000477e2ef /data/app/~~iqNzeqm6H35xOHwrI-bDjQ==/com.google.android.trichromelibrary_636705433-LrOgBRHApr9q42tJ7YTurQ==/base.apk (offset 0x8dc000)
#06 pc 0x0000000005f58d33 /data/app/~~iqNzeqm6H35xOHwrI-bDjQ==/com.google.android.trichromelibrary_636705433-LrOgBRHApr9q42tJ7YTurQ==/base.apk (offset 0x8dc000)
#07 pc 0x0000000005f0b0f3 /data/app/~~iqNzeqm6H35xOHwrI-bDjQ==/com.google.android.trichromelibrary_636705433-LrOgBRHApr9q42tJ7YTurQ==/base.apk (offset 0x8dc000)
#08 pc 0x0000000005f0ab77 /data/app/~~iqNzeqm6H35xOHwrI-bDjQ==/com.google.android.trichromelibrary_636705433-LrOgBRHApr9q42tJ7YTurQ==/base.apk (offset 0x8dc000)

       at org.chromium.base.JniAndroid.handleException(chromium-TrichromeWebViewGoogle6432.aab-stable-636705433:21)
       at J.N.M1Y_XVCN(chromium-TrichromeWebViewGoogle6432.aab-stable-636705433)
       at org.chromium.content.browser.BrowserStartupControllerImpl.d(chromium-TrichromeWebViewGoogle6432.aab-stable-636705433:110)
       at WV.M5.run(chromium-TrichromeWebViewGoogle6432.aab-stable-636705433:198)
       at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:487)
       at java.util.concurrent.FutureTask.run(FutureTask.java:264)
       at org.chromium.base.task.PostTask.d(chromium-TrichromeWebViewGoogle6432.aab-stable-636705433:11)
       at org.chromium.android_webview.AwBrowserProcess.j(chromium-TrichromeWebViewGoogle6432.aab-stable-636705433:33)
       at com.android.webview.chromium.L.d(chromium-TrichromeWebViewGoogle6432.aab-stable-636705433:203)
       at com.android.webview.chromium.L.b(chromium-TrichromeWebViewGoogle6432.aab-stable-636705433:42)
       at com.android.webview.chromium.L.f(chromium-TrichromeWebViewGoogle6432.aab-stable-636705433:4)
       at com.android.webview.chromium.WebViewChromiumFactoryProvider.l(chromium-TrichromeWebViewGoogle6432.aab-stable-636705433:8)
       at com.android.webview.chromium.WebViewChromium.init(chromium-TrichromeWebViewGoogle6432.aab-stable-636705433:97)
       at android.webkit.WebView.<init>(WebView.java:448)
       at android.webkit.WebView.<init>(WebView.java:368)
       at android.webkit.WebView.<init>(WebView.java:350)
       at android.webkit.WebView.<init>(WebView.java:337)
       at android.webkit.WebView.<init>(WebView.java:327)
       at com.tealium.internal.dispatcher.WebViewDispatcher$b.run(WebViewDispatcher.java:5)
       at android.os.Handler.handleCallback(Handler.java:958)
       at android.os.Handler.dispatchMessage(Handler.java:99)
       at android.os.Looper.loopOnce(Looper.java:222)
       at android.os.Looper.loop(Looper.java:314)
       at android.app.ActivityThread.main(ActivityThread.java:8706)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:565)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1081)

We detected a new issue b/337584810 being duplicated to this closed issue automatically, and we have set b/337584810 as the current canonical bug, please check if any action needs to be taken.

If you think this is a bad suggestion, please file a bug.

I'm seeing the same issue. Can I have access to the following ticket? b/337584810

Thread Name: java.util.ConcurrentModificationException
  android.util.ArrayMap.put (ArrayMap.java:607)
  android.os.PowerManager.addThermalStatusListener (PowerManager.java:3233)
  android.os.PowerManager.addThermalStatusListener (PowerManager.java:3205)
  org.chromium.base.PowerMonitor.a (chromium-TrichromeWebViewGoogle6432.aab-stable-631212133:88)
  org.chromium.base.PowerMonitor.isBatteryPower (chromium-TrichromeWebViewGoogle6432.aab-stable-631212133:5)
  J.N.M1Y_XVCN (Native Method)
  org.chromium.content.browser.BrowserStartupControllerImpl.d (chromium-TrichromeWebViewGoogle6432.aab-stable-631212133:110)
  WV.h5.run (chromium-TrichromeWebViewGoogle6432.aab-stable-631212133:180)
  java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:487)
  java.util.concurrent.FutureTask.run (FutureTask.java:264)
  org.chromium.base.task.PostTask.d (chromium-TrichromeWebViewGoogle6432.aab-stable-631212133:11)
  org.chromium.android_webview.AwBrowserProcess.j (chromium-TrichromeWebViewGoogle6432.aab-stable-631212133:32)
  com.android.webview.chromium.E.d (chromium-TrichromeWebViewGoogle6432.aab-stable-631212133:188)
  com.android.webview.chromium.E.b (chromium-TrichromeWebViewGoogle6432.aab-stable-631212133:42)
  com.android.webview.chromium.E.f (chromium-TrichromeWebViewGoogle6432.aab-stable-631212133:4)
  com.android.webview.chromium.WebViewChromiumFactoryProvider.l (chromium-TrichromeWebViewGoogle6432.aab-stable-631212133:8)
  com.android.webview.chromium.WebViewChromium.init (chromium-TrichromeWebViewGoogle6432.aab-stable-631212133:97)
  android.webkit.WebView.<init> (WebView.java:444)
  android.webkit.WebView.<init> (WebView.java:364)
  android.webkit.WebView.<init> (WebView.java:346)
  android.webkit.WebView.<init> (WebView.java:333)
  android.webkit.WebView.<init> (WebView.java:323)
  com.google.android.gms.ads.internal.webview.ag.<init>
  com.google.android.gms.ads.internal.webview.s.a
  com.google.android.gms.ads.internal.webview.w.a
  com.google.android.gms.ads.internal.js.k.<init>
  com.google.android.gms.ads.internal.js.r.run
  android.os.Handler.handleCallback (Handler.java:958)
  android.os.Handler.dispatchMessage (Handler.java:99)
  m.azn.a
  com.google.android.gms.ads.internal.util.zzaf.a
  m.azn.dispatchMessage
  android.os.Looper.loopOnce (Looper.java:230)
  android.os.Looper.loop (Looper.java:319)
  android.app.ActivityThread.main (ActivityThread.java:8893)
  java.lang.reflect.Method.invoke (Native Method)
  com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:608)
  com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1103)

Also visible for me:

android.content.res.Resources$NotFoundException: Resource ID #0x20c0006
    at android.content.res.ResourcesImpl.getValue(ResourcesImpl.java:238)
    at android.content.res.Resources.getInteger(Resources.java:1192)
    at org.chromium.ui.base.DeviceFormFactor.isTablet(chromium-TrichromeWebViewGoogle.aab-stable-636712330:9)
    at android.os.MessageQueue.nativePollOnce(MessageQueue.java)
    at android.os.MessageQueue.next(MessageQueue.java:335)
    at android.os.Looper.loopOnce(Looper.java:161)
    at android.os.Looper.loop(Looper.java:288)
    at android.app.ActivityThread.main(ActivityThread.java:7886)
    at java.lang.reflect.Method.invoke(Method.java)
    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:568)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1045)
org.chromium.base.JniAndroid$UncaughtExceptionException: Native stack trace:
#00 pc 0x031490ed /data/app/~~cpqTRpiPd16pTL2tLIK1Ew==/com.google.android.trichromelibrary_636712330-Q2X7Rgz8X3NCjCqquvRhCg==/base.apk (offset 0x8d8000)
#01 pc 0x026484dd /data/app/~~cpqTRpiPd16pTL2tLIK1Ew==/com.google.android.trichromelibrary_636712330-Q2X7Rgz8X3NCjCqquvRhCg==/base.apk (offset 0x8d8000)
#02 pc 0x00e49cf1 /data/app/~~cpqTRpiPd16pTL2tLIK1Ew==/com.google.android.trichromelibrary_636712330-Q2X7Rgz8X3NCjCqquvRhCg==/base.apk (offset 0x8d8000)
#03 pc 0x03018947 /data/app/~~cpqTRpiPd16pTL2tLIK1Ew==/com.google.android.trichromelibrary_636712330-Q2X7Rgz8X3NCjCqquvRhCg==/base.apk (offset 0x8d8000)
#04 pc 0x030600a3 /data/app/~~cpqTRpiPd16pTL2tLIK1Ew==/com.google.android.trichromelibrary_636712330-Q2X7Rgz8X3NCjCqquvRhCg==/base.apk (offset 0x8d8000)
#05 pc 0x0306004d /data/app/~~cpqTRpiPd16pTL2tLIK1Ew==/com.google.android.trichromelibrary_636712330-Q2X7Rgz8X3NCjCqquvRhCg==/base.apk (offset 0x8d8000)
#06 pc 0x03018d7b /data/app/~~cpqTRpiPd16pTL2tLIK1Ew==/com.google.android.trichromelibrary_636712330-Q2X7Rgz8X3NCjCqquvRhCg==/base.apk (offset 0x8d8000)
#07 pc 0x03058ac1 /data/app/~~cpqTRpiPd16pTL2tLIK1Ew==/com.google.android.trichromelibrary_636712330-Q2X7Rgz8X3NCjCqquvRhCg==/base.apk (offset 0x8d8000)
#08 pc 0x03058975 /data/app/~~cpqTRpiPd16pTL2tLIK1Ew==/com.google.android.trichromelibrary_636712330-Q2X7Rgz8X3NCjCqquvRhCg==/base.apk (offset 0x8d8000)
#09 pc 0x03a87079 /data/app/~~cpqTRpiPd16pTL2tLIK1Ew==/com.google.android.trichromelibrary_636712330-Q2X7Rgz8X3NCjCqquvRhCg==/base.apk (offset 0x8d8000)
#10 pc 0x03a8792f /data/app/~~cpqTRpiPd16pTL2tLIK1Ew==/com.google.android.trichromelibrary_636712330-Q2X7Rgz8X3NCjCqquvRhCg==/base.apk (offset 0x8d8000)
#11 pc 0x020d614b /data/app/~~cpqTRpiPd16pTL2tLIK1Ew==/com.google.android.trichromelibrary_636712330-Q2X7Rgz8X3NCjCqquvRhCg==/base.apk (offset 0x8d8000)
#12 pc 0x020d614b /data/app/~~cpqTRpiPd16pTL2tLIK1Ew==/com.google.android.trichromelibrary_636712330-Q2X7Rgz8X3NCjCqquvRhCg==/base.apk (offset 0x8d8000)
#13 pc 0x020d614b /data/app/~~cpqTRpiPd16pTL2tLIK1Ew==/com.google.android.trichromelibrary_636712330-Q2X7Rgz8X3NCjCqquvRhCg==/base.apk (offset 0x8d8000)
#14 pc 0x03c402af /data/app/~~cpqTRpiPd16pTL2tLIK1Ew==/com.google.android.trichromelibrary_636712330-Q2X7Rgz8X3NCjCqquvRhCg==/base.apk (offset 0x8d8000)
#15 pc 0x020d614b /data/app/~~cpqTRpiPd16pTL2tLIK1Ew==/com.google.android.trichromelibrary_636712330-Q2X7Rgz8X3NCjCqquvRhCg==/base.apk (offset 0x8d8000)
#16 pc 0x02b64d25 /data/app/~~cpqTRpiPd16pTL2tLIK1Ew==/com.google.android.trichromelibrary_636712330-Q2X7Rgz8X3NCjCqquvRhCg==/base.apk (offset 0x8d8000)
#17 pc 0x02652053 /data/app/~~cpqTRpiPd16pTL2tLIK1Ew==/com.google.android.trichromelibrary_636712330-Q2X7Rgz8X3NCjCqquvRhCg==/base.apk (offset 0x8d8000)
#18 pc 0x0264f59b /data/app/~~cpqTRpiPd16pTL2tLIK1Ew==/com.google.android.trichromelibrary_636712330-Q2X7Rgz8X3NCjCqquvRhCg==/base.apk (offset 0x8d8000)
#19 pc 0x01d71ccd /data/app/~~cpqTRpiPd16pTL2tLIK1Ew==/com.google.android.trichromelibrary_636712330-Q2X7Rgz8X3NCjCqquvRhCg==/base.apk (offset 0x8d8000)
#20 pc 0x01d7e23f /data/app/~~cpqTRpiPd16pTL2tLIK1Ew==/com.google.android.trichromelibrary_636712330-Q2X7Rgz8X3NCjCqquvRhCg==/base.apk (offset 0x8d8000)
#21 pc 0x01d7e20f /data/app/~~cpqTRpiPd16pTL2tLIK1Ew==/com.google.android.trichromelibrary_636712330-Q2X7Rgz8X3NCjCqquvRhCg==/base.apk (offset 0x8d8000)
#22 pc 0x0308b5e1 /data/app/~~cpqTRpiPd16pTL2tLIK1Ew==/com.google.android.trichromelibrary_636712330-Q2X7Rgz8X3NCjCqquvRhCg==/base.apk (offset 0x8d8000)
#23 pc 0x000072dd /system/lib/libutils.so
#24 pc 0x00006fd1 /system/lib/libutils.so
#25 pc 0x0006bc6d /system/lib/libandroid_runtime.so

    at org.chromium.base.JniAndroid.handleException(chromium-TrichromeWebViewGoogle.aab-stable-636712330:21)
    at android.os.MessageQueue.nativePollOnce(MessageQueue.java)
    at android.os.MessageQueue.next(MessageQueue.java:335)
    at android.os.Looper.loopOnce(Looper.java:161)
    at android.os.Looper.loop(Looper.java:288)
    at android.app.ActivityThread.main(ActivityThread.java:7886)
    at java.lang.reflect.Method.invoke(Method.java)
    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:568)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1045)

We detected a new issue b/337584810 being duplicated to this closed issue automatically, and we have set b/337584810 as the current canonical bug, please check if any action needs to be taken.

I do not have access to see and follow up on the new issue. Could you make this public?

This issue is still occurring in the latest WebView version for us.

Hi,I have face same issue from firebase Crahyltics reported.

We detected a new issue b/337584810 being duplicated to this closed issue automatically, and we have set b/337584810 as the current canonical bug, please check if any action needs to be taken.

Hello, Could you please give us access to this issue? Thank you

Hello, Could you please give us access to this issue? Thank you

Hi, that bug shouldn't have been made the canonical bug. This is the canonical public bug outlining this issue.

We detected a new issue b/348555655 being duplicated to this closed issue automatically, please check if there is more information in b/348555655 for further analysis.

If you think this is a bad suggestion, please file a bug.

Hi, Please provide access to b/348555655 issue.

As mentioned above, "We detected a new issue b/348555655 being duplicated to this closed issue automatically, please check if there is more information in b/348555655 for further analysis."

Everyone: please see comment 6 and comment 9 above. This is not a new crash and it is not actionable. We changed how WebView reports uncaught Java exceptions in JNI so that the Java exception is actually included in the report, which meant that a lot of older native crashes that were already happening started being reported as Java exceptions instead.

The actual problem here is a longstanding issue with Android's resource handling and we're working on platform changes to address the root cause, as well as improving the existing workarounds in WebView, but there is nothing we can do to investigate any particular case unless you can tell us how to reliably reproduce it.

We detected a new issue b/353862916 being duplicated to this closed issue automatically, please check if there is more information in b/353862916 for further analysis.

If you think this is a bad suggestion, please file a bug.

I'm facing the same issue

I love how all these crashes beautifully stack up in crashlytics the more android components you use in application. At least this one is not so old, I am following other issue tickets that are more than year old and still "Assigned". Hopefully we will receive some fixes soon.

Unfortunately this crash has been happening since at least Android 7 (or earlier for some apps), so it is in fact very old :(

It's just that it used to be reported as a native crash that was hard for developers to understand, unless they happened to have a copy of the logcat output that contained the Resources$NotFoundException that is the real cause. We changed how Java exceptions that reach native code are reported in WebView 121 so that the Java exception is more clearly shown, but the actual underlying cause has not changed and this isn't a new issue, it just changed from one crash signature to another around the beginning of 2024.

Android 15 beta 2 and later contain a framework fix for this issue and so far we have seen zero reports of this crash still occurring on current Android 15 versions, so hopefully this will soon be resolved for the latest OS version. Unfortunately, the framework change to resolve this is quite complex and it's not realistically possible to include it in updates to older OS versions.

We are experimenting with a new workaround for the problem on older OS versions now that it should be fixed "for real" on future ones, but the workaround changes some of the functionality of WebView's UI elements in ways that may not be acceptable for all apps, so it's still being iterated on and we're not yet able to give a timeline or confirm that it will definitely be possible to release.

The changes in Android 15 to avoid this issue are the introduction of the new API https://developer.android.com/reference/android/content/res/Resources#registerResourcePaths(java.lang.String,%20android.content.pm.ApplicationInfo) which WebView now uses instead of the previous unreliable mechanism. This was implemented by a number of separate changes and fixes during Android 15 development and I'm not sure I can easily determine the complete list. What do you actually want to do?

same for me a large number of crashes

This crash has highest number of occurrence on our app.

• 99% on Xiaomi Devices
• 99% on android 12 & 14 (27% and 72% respectively)
• 100% while app on background and proximity ON

Below is an update on the current state of this issue.

Context

WebView has access to two Contexts. The first is its own that is created when WebView is loaded. The second is the host app’s Context. WebView currently loads its own resources into the host app’s Context so that the host app can influence how WebView UI renders and can match WebView’s UI to its own. However, sometimes a host app inadvertently affects WebView’s resources when trying to make changes to its own resources which can invalidate the cached resource IDs within WebView’s own code. This means that when WebView tries to lookup one of its own resources using the old ID, it hits a Resource$NotFoundException.

The problem

We don’t know why, but the number of occurrences of this crash has steadily increased over the past year. We were able to get a fix put in place in the platform for Android V (see comment#57) but this doesn’t resolve the issue for older versions of Android. We’ve come up with a solution for those older Android versions which will roll out in WebView M134, slated for release on March 4th.

Our solution

Our fix for this crash is to no longer inject WebView’s resources into the host app’s Context. Instead, we will refer to our own resources inside WebView’s own Context which will prevent the host app’s code from invalidating our resource IDs. In theory, this should completely eliminate Resource$NotFoundExceptions of this type in WebView. Unfortunately, we won’t be able to verify that until the fix is rolled out generally. We’ve asked partners and some Google first party apps to test this fix and the results so far have been overwhelmingly positive.

Caveats

As WebView will no longer be accessing resources through the host app’s Context, the host app will no longer be able to dictate how WebView’s UI should be styled. Instead, WebView’s UI moving forward will use the device’s default theme. This will be a Material theme for older devices and a Material You theme for newer devices which support it.

I can confirm, in our case we see a visible and significant drop in the number of related crashes starting Feb 25-27.

But strangely, we cannot relate it to Android WebView v134 because based on what we see for our users v134 started being adopted only on ~March 5.

Based on our data below versions were more aligned with the crashes decreasing:

• Android System WebView (133.0.6943.122)
• Android System WebView (133.0.6943.137)

Also, it may be worth mentioning that unfortunately on our side, around the same time (Feb 26) we took another action to mitigate the issue - we removed Akamai SDK (v4.0.2). It did some weird things with WebView internally, so the SDK was under suspicion on our side because integrating it in the past also matched the time when we started receiving such WebView crashes.

Changing how you use WebView, especially if you change the timing of when you are invoking any WebView-related APIs early in your app's startup, is often going to change how likely it is that you encounter this issue. It's not really about whether the usage is "weird" or not, it's just about the timing of when APIs are first called (and on what thread) and what else is going on in the process at the same time.

So, it's likely that the significant drop for you was caused by removing that SDK, rather than by the M134 rollout.

The M134 rollout did begin on 26th Feb but this is the "early stable" rollout that is only distributed to 0.1% of users so at that stage it's not going to make a significant impact to the crash rates. The main rollout (to 1% and then gradually increasing) did not start until 4th March and is currently being distributed to 25% of users; it should go to 100% in the next few days.

We are getting the same crash in our app after adding WebSettings.getDefaultUserAgent(context). Also majorly Xiaomi, but specifically android go devices (Redmi A1/A1+/A3, Vivo V2120). Was calling this inside a service's onCreate in background thread (as initial call was taking upwards of 200ms)