New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 758519 link

Starred by 5 users
Status: WontFix
Owner: ----
Closed: Jan 2018
Cc:
█ sandeepkumars@chromium.org
ligim...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

chromium crash for Android api24

Reported by zhang...@conew.com, Aug 24 2017 
Steps to reproduce the problem:
N/A

What is the expected behavior?

What went wrong?
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?

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:

Comment 1 by sandeepkumars@chromium.org, Aug 25 2017

Cc: sandeepkumars@chromium.org
Labels: Needs-Feedback
@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!!

Comment 2 by zhang...@conew.com, 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
dump.zip
15.4 KB Download
Project Member

Comment 3 by sheriffbot@chromium.org, Aug 25 2017

Labels: -Needs-Feedback
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

Comment 4 by sandeepkumars@chromium.org, Aug 29 2017

Labels: TE-DesktopTriage

Comment 5 by ligim...@chromium.org, Oct 25 2017

Cc: ligim...@chromium.org
Labels: -TE-DesktopTriage Stability-Crash Triaged-Mobile
From the dump file seems like the crash got triggered in ResourceExtractor.java:78, which is fixed in Issue 697679, lopping to Andrew for confirming whether the root cause is the same.

zhangbo5@ are you still facing the crash?

Comment 6 by ligim...@chromium.org, Oct 25 2017 

 Issue 758088  has been merged into this issue.

Comment 7 by msrchandra@chromium.org, Oct 30 2017

Labels: Needs-Feedback

Comment 8 by sandeepkumars@chromium.org, Dec 8 2017 

@zhangbo5: Could you please upgrade your Chrome to latest stable #63.0.3239.83 and check if you still face the issue?

Thanks!!

Comment 9 by dtapu...@chromium.org, Jan 23 2018

Status: WontFix (was: Unconfirmed)
Closing issue due to lack of feedback requested but not provided. If the issue still exists please open a new issue with the details requested.
►

Sign in to add a comment