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

Issue 786288 link

Starred by 3 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug-Regression



Sign in to add a comment

Regression : Unable to load the page after clicking on 'Open all' option in chrome://history/syncedTabs

Reported by rp...@etouch.net, Nov 17 2017

Issue description

Version: 64.0.3271.0 71f07f2c6c77c9e67158a193516e2f0c6229ce64-refs/heads/master@{#517250}
OS: Linux (14.04 LTS)
Pre condition : sign in to chrome with valid credentials.

What steps will reproduce the problem?
1. Launch chrome, navigate chrome://history page and click on 'Tabs from other devices' 
2. Now click on 'Actions' iron icon and then click on 'Open all' and observe history page

Actual: Page gets stuck after clicking on 'Open all' option in chrome://history
Expected: Page shouldn't get stuck after clicking on 'Open all' option in chrome://history

This is regression issue, broken in ‘M 64’ and will soon update other info:

 

Comment 1 by rp...@etouch.net, Nov 17 2017

Components: UI>Browser>History
Labels: hasbisect
Owner: tzik@chromium.org
Status: Assigned (was: Unconfirmed)
Summary: Regression : Unable to load the page after clicking on 'Open all' option in chrome://history/syncedTabs (was: Regression : History page gets stuck after clicking on 'Open all' option in chrome://history)
Correction :

Actual : Unable to load the page after clicking on 'Open all' option in chrome://history/syncedTabs
Expected : Should be able to load the page after clicking on 'Open all' option in chrome://history/syncedTabs

This is regression issue, broken in ‘M 63’ and below is the bisect results:
Good build:63.0.3216.0 (Revision: 502109)
Bad build: 63.0.3217.0 (Revision: 502454)

Below is the Change Lg :
https://chromium.googlesource.com/chromium/src/+log/63.0.3216.0..63.0.3217.0?pretty=fuller&n=10000
(Unable to narrow down the range using tool bisect hence providing Change Log)

Suspect : https://chromium.googlesource.com/chromium/src/+/5b957db1a476b8e3083d3e208dbf2a17416d0d95

@tzik- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

Note : Above issue is not seen on Mac and Windows OS.

Comment 2 by rp...@etouch.net, Nov 17 2017

Labels: -M-64 M-63

Comment 3 by rp...@etouch.net, Nov 17 2017

Kindly refer the below link for screen cast.

https://drive.google.com/drive/folders/1jDrGcoA6tA3PTawJsj_GlNCdq46GBjlG?usp=sharing
Labels: ReleaseBlock-Stable
Adding release blocker for this issue.Please undo if not the case.

Thank You!

Comment 5 by gov...@chromium.org, Nov 17 2017

M63 Stable promotion is coming VERY soon. Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and request a merge  into the release branch ASAP. Thank you.

Comment 6 by tzik@chromium.org, Nov 20 2017

Owner: ----
Status: Untriaged (was: Assigned)
Rerouting to History team. It's likely unrelated to my change.
Cc: calamity@chromium.org

Comment 8 by gov...@chromium.org, Nov 20 2017

M63 Stable promotion is coming VERY soon. Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and request a merge  into the release branch ASAP. Thank you.
Cc: groby@chromium.org dpa...@chromium.org
Labels: -Pri-1 -ReleaseBlock-Stable Pri-3
Status: Available (was: Untriaged)
This seems to only happen with many instances of the History page. Other pages aren't affected. This likely to do with the way we create and serve WebUIs, which gets confused when we try to load several windows with the history page at once. A similar thing happens when multiple MD Bookmarks tabs are foreground loaded.

ccing WebUI backend gurus and deprioritizing.
Project Member

Comment 10 by sheriffbot@chromium.org, Nov 21

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment