New issue
Advanced search Search tips

Issue 841452 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 783562
Owner: ----
Closed: May 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Chrome closes after closing all tabs

Reported by jeremy.v...@gmail.com, May 9 2018

Issue description

Chrome Version       : 66.0.3359.126
OS Version: 
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari:
    Firefox:
    IE/Edge:

What steps will reproduce the problem?
1. Click the in browser tab button.
2. Click "x" in the top right of the tab selection until all tabs are closed.
3. The default black no tabs open window will be shown briefly before Chrome will crash back to the home screen. 

What is the expected result?

Prior to the recent update, the black new tab window would be shown after closing all tabs. 
What happens instead of that?


Please provide any additional information below. Attach a screenshot if
possible.

UserAgentString: Mozilla/5.0 (Linux; Android 8.1.0; Nexus 5X Build/OPM3.171019.016) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.126 Mobile Safari/537.36


Will edit with screen shots shortly.
 
Screenshot of the page I am mentioning above attached.


15258899913044129090729348277379.jpg
261 KB View Download
Clicking the close button on the one remaining tab above would leave the black window behind open. 

After the update, closing the last tab crashes/closes Chrome after about 1 second on the black empty tab window.
Labels: Needs-Triage-M66
Noticed this tonight too - a message sometimes appears when it crashes back to home screen - "app isn't installed."
Components: UI>Browser
Labels: Triaged-ET OS-Android
As per comment#0 and screenshot in comment#1 this issue seems to be specific to OS=Android. Hence adding appropriate label.

Thanks!
Labels: Needs-triage-Mobile Triaged-Mobile
Mergedinto: 783562
Status: Duplicate (was: Unconfirmed)
This issue seems to be duplicate of the  Issue 783562 . Hence, mergining into it.

Thanks!

Sign in to add a comment