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

Issue 606015 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Nov 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug
Team-Security-UX



Sign in to add a comment

Interstitial crash on Android

Project Member Reported by lgar...@chromium.org, Apr 22 2016

Issue description

Chrome 52.0.2713.0 Canary
Android 6.0.1
Nexus 5X

What steps will reproduce the problem?
(1) Visit badssl.com
(2) Click on "expired"


What is the expected output?
An interstitial loads.

What do you see instead?
Crash

The same happens for wrong.host.badssl.com and self-signed.badssl.com
I can reproduce reliable on Chrome Canary on this device, but not on other channels or other devices.

I've attached the output of `adb logca`t | grep Chrome (interstitial-crash-logcat.txt) and `adb logcat | grep -e chrome_process1 -e chrome_process2 -e chrome_process3` (interstitial-crash-logcat2.txt). I can't figure out how to get the actual crash report in `/data/user/0/com.chrome.canary/cache/Crash Reports`; all the Google results are targeted at Android developers getting crash logs for their apps, or talk about rooting.

I'm afraid to upgrade Chrome or reboot the device, in case that will make it impossible to track down a real problem.
 
interstitial-crash-logcat.txt
11.0 KB View Download
interstitial-crash-logcat-2.txt
48.7 KB View Download
Labels: Interstitials

Comment 2 by mea...@chromium.org, Nov 22 2016

Status: WontFix (was: Assigned)
Can't repro anymore.
Components: -Security>UX UI>Browser>Interstitials

Sign in to add a comment