New issue
Advanced search Search tips

Issue 677905 link

Starred by 2 users

Issue metadata

Status: Duplicate
Owner: ----
Closed: Jan 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

[Chrome][M55][Android 7.0] Crash caused by: android.content.res.Resources$NotFoundException

Reported by seiyon.p...@gmail.com, Jan 3 2017

Issue description

Steps to reproduce the problem:
1. Launch Chrome

What is the expected behavior?
User can launch Chrome without crashes.

What went wrong?
Chrome crashes

Crashed report ID: 

How much crashed? Whole browser

Is it a problem with a plugin? N/A 

Did this work before? N/A 

Chrome version: 55.0.2883.87  Channel: stable
OS Version: 7.0
Flash Version: Shockwave Flash 24.0 r0

Chrome 52, 53, 55 crashes due to  android.content.res.Resources$NotFoundException.

12-26 11:51:35.574 8275 11185 E AndroidRuntime: FATAL EXCEPTION: AsyncTask #5
12-26 11:51:35.574 8275 11185 E AndroidRuntime: Process: com.android.chrome, PID: 8275
12-26 11:51:35.574 8275 11185 E AndroidRuntime: java.lang.RuntimeException: An error occurred while executing doInBackground()
12-26 11:51:35.574 8275 11185 E AndroidRuntime: at android.os.AsyncTask$3.done(AsyncTask.java:318)
12-26 11:51:35.574 8275 11185 E AndroidRuntime: at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:354)
12-26 11:51:35.574 8275 11185 E AndroidRuntime: at java.util.concurrent.FutureTask.setException(FutureTask.java:223)
12-26 11:51:35.574 8275 11185 E AndroidRuntime: at java.util.concurrent.FutureTask.run(FutureTask.java:242)
12-26 11:51:35.574 8275 11185 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
12-26 11:51:35.574 8275 11185 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
12-26 11:51:35.574 8275 11185 E AndroidRuntime: at java.lang.Thread.run(Thread.java:761)
12-26 11:51:35.574 8275 11185 E AndroidRuntime: Caused by: android.content.res.Resources$NotFoundException: Resource ID #0x7f09000a
12-26 11:51:35.574 8275 11185 E AndroidRuntime: at android.content.res.ResourcesImpl.getValue(ResourcesImpl.java:208)
12-26 11:51:35.574 8275 11185 E AndroidRuntime: at android.content.res.ResourcesImpl.openRawResource(ResourcesImpl.java:317)
12-26 11:51:35.574 8275 11185 E AndroidRuntime: at android.content.res.Resources.openRawResource(Resources.java:1246)
12-26 11:51:35.574 8275 11185 E AndroidRuntime: at android.content.res.Resources.openRawResource(Resources.java:1191)
12-26 11:51:35.574 8275 11185 E AndroidRuntime: at org.chromium.base.ResourceExtractor$ExtractTask.doInBackground$51DKOQJ1EPGIUR31DPJIULJFD5I3MAACD9GNCO9FDHGMSPPFAPNMIP1R(ResourceExtractor.java:2118)
12-26 11:51:35.574 8275 11185 E AndroidRuntime: at org.chromium.base.ResourceExtractor$ExtractTask.doInBackground(ResourceExtractor.java:56)
12-26 11:51:35.574 8275 11185 E AndroidRuntime: at android.os.AsyncTask$2.call(AsyncTask.java:304)
12-26 11:51:35.574 8275 11185 E AndroidRuntime: at java.util.concurrent.FutureTask.run(FutureTask.java:237)
12-26 11:51:35.574 8275 11185 E AndroidRuntime: ... 3 more
12-26 11:51:35.643 1296 5484 W ActivityManager: Force finishing activity com.android.chrome/org.chromium.chrome.browser.ChromeTabbedActivity
 
[M52].zip
15.2 MB Download
[M53].zip
4.3 MB Download
[M55].zip
5.2 MB Download
Labels: Stability-Sheriff-Android
Cc: agrieve@chromium.org
agrieve@, resource 0x7f09000a is "<public type="raw" name="en_us" id="0x7f09000a" />" in 55.0.2883.87 according to apktool, so this crash is related to issue 653771?
Mergedinto: 653771
Status: Duplicate (was: Unconfirmed)
Sounds like it. So, should be fixed as of Chrome 56 (the bug is a bit confusing since there last commit is a revert, but that was to a branch, so the fix actually did stick as https://codereview.chromium.org/2404253003.

Also related is  bug 673458 , which didn't get fixed until M57.

Either way, it should be sufficient to clear Chrome's data through the Android app manager to fix this up.
@grieve@chromium.org, it seems that comment 3 makes me confused.
Could you assure which version will include the fix and be rolled out via Play store? 
For this exception - M56 has the fix.
Thanks for prompt feedback.

Sign in to add a comment