Issue metadata
Sign in to add a comment
|
org.chromium.base.ResourceExtractor crash
Reported by
zhang...@conew.com,
Aug 23 2017
|
||||||||||||||||||||||
Issue descriptionSteps to reproduce the problem: I do not know how to cause crash,just has crash message。 What is the expected behavior? What went wrong? 。。。 Did this work before? N/A Does this work in other browsers? N/A Chrome version: Channel: n/a OS Version: Android 7.0 Flash Version:
,
Aug 23 2017
java.lang.RuntimeException: An error occurred while executing doInBackground() at android.os.AsyncTask$3.done(AsyncTask.java:318) at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:354) at java.util.concurrent.FutureTask.setException(FutureTask.java:223) at java.util.concurrent.FutureTask.run(FutureTask.java:242) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607) at java.lang.Thread.run(Thread.java:762) Caused by: java.lang.RuntimeException at org.chromium.base.ResourceExtractor$ExtractTask.doInBackground$51DKOQJ1EPGIUR31DPJIULJFD5I3MAACD9GNCO9FDHGMSPPFAPNMIP1R0(ResourceExtractor.java:24) at org.chromium.base.ResourceExtractor$ExtractTask.doInBackground(ResourceExtractor.java:78) at android.os.AsyncTask$2.call(AsyncTask.java:304) at java.util.concurrent.FutureTask.run(FutureTask.java:237) ... 3 more java.lang.RuntimeException at org.chromium.base.ResourceExtractor$ExtractTask.doInBackground$51DKOQJ1EPGIUR31DPJIULJFD5I3MAACD9GNCO9FDHGMSPPFAPNMIP1R0(ResourceExtractor.java:24) at org.chromium.base.ResourceExtractor$ExtractTask.doInBackground(ResourceExtractor.java:78) at android.os.AsyncTask$2.call(AsyncTask.java:304) at java.util.concurrent.FutureTask.run(FutureTask.java:237) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607) at java.lang.Thread.run(Thread.java:762)
,
Aug 23 2017
Our application recently collected some information about the collapse of chromium, according to the feedback, the crashed phone is 7.0, API24, and the crashed model is concentrated in samsung, LGE, MOTOROLA, Sony, etc.It's all broken down in the way our own process, and we're skeptical about using webview, but there's no specific information on the stack.I haven't received this kind of crash before, and I wonder if it's related to the recent Android changes?
,
Aug 25 2017
@zhangbo5: Thanks for the report!! Could you please provide us the steps to reproduce the problem, Chrome version, details of your device and attach a crash server I'd by navigating to chrome://crashes. That would help us in triaging of the issue. Thanks!!
,
Aug 25 2017
Hello, we don't know the steps and the chrome version. We collected through our crash platform.Some of the crash information we collected in the attachment.According to this information, the crash is centered on android 7.0 and above
,
Aug 25 2017
Thank you for providing more feedback. Adding requester "sandeepkumars@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 28 2017
Hi, is it possible that the changes done on this: https://bugs.chromium.org/p/chromium/issues/detail?id=752510 might have caused this issue starting on many android apps?
,
Aug 29 2017
,
Oct 25 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by zhang...@conew.com
, Aug 23 2017