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

Issue 636775 link

Starred by 2 users
Status: Fixed
Owner:
kenrb@chromium.org
Closed: Dec 2016
Cc:
calamity@chromium.org
nyerramilli@chromium.org
█ ranjitkan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Regression: Chrome://history page becomes blank after back/forward navigation.

Reported by rk...@etouch.net, Aug 11 2016 
Chrome Version: 54.0.2826.0 Revision 58bed46055a79ffc0dc4210601d260e3b3e75dbc-refs/heads/master@{#411209} 
OS: Mac(10.10.5, 10.11.4)

What steps will reproduce the problem?
(1) Launch chrome, navigate to chrome://history then right click on page and select 'View source page'.
(2) Come back to chrome://history page, click on back navigation button then forward navigation button.
(3) wait 1 sec and observe.

Actual: Chrome://history page becomes blank after back/forward navigation.

Expected: Chrome://history page should not get blank after back/forward navigation.

This is a regression issue, broken in 'M-54', will soon update the other info:

Comment 1 by rk...@etouch.net, Aug 11 2016

Labels: hasbisect
Owner: calamity@chromium.org
Status: Assigned (was: Unconfirmed)
Good Build: 54.0.2825.0
Bad Build: 54.0.2826.0

Narrow Bisect:
https://chromium.googlesource.com/chromium/src/+log/8fcbc602fb75514f4270b86377009cd787c24222..c34b20c196d32daae5764098479936bc7e10e61f?pretty=fuller&n=100

Suspecting: r410972 ?

Note: Issue is not seen on Windows and Linux OS.

Comment 2 by rk...@etouch.net, Aug 11 2016

Actual_History.mov
1.6 MB Download

Comment 3 by ranjitkan@chromium.org, Aug 11 2016

Labels: ReleaseBlock-Beta
Adding release block label, please undo if not the case.

Comment 4 by creis@chromium.org, Aug 11 2016

Cc: kenrb@chromium.org
This looks a lot like kenrb's StartNewContentRenderingTimeout timer from  issue 497588 , which displays white if we don't get a paint IPC 2 seconds after a cross-document navigation commits (to prevent URL spoofs where the renderer hangs after commit but before painting anything).  Side note for Ken: it's a bit strange that the links still work on the white page.  :(

It does seem specific to Mac, since I can't repro on Windows.  We've seen similar regressions in  issue 535375 .

calamity@: Is there something in your history work that might be triggering that (e.g., a navigation commit with no subsequent paint IPC)?

Comment 5 by calamity@chromium.org, Aug 16 2016 

Nothing comes to mind.. We do use history.pushState() if that affects anything?

Comment 6 by ranjitkan@chromium.org, Aug 23 2016 

Gentle Ping, Issue is marked with a Beta blocker and M54 is approaching Beta soon. Could someone please take a look into it as this is still an issue on canary build 54.0.2836.0 for MAC 10.11.6.

Thanks.!

Comment 7 by calamity@chromium.org, Aug 23 2016

Cc: -kenrb@chromium.org calamity@chromium.org
Labels: -Pri-1 -ReleaseBlock-Beta Pri-2
Owner: kenrb@chromium.org
I can't repro this on 54.0.2836.0 mac canary. Either way, I wouldn't call this a release blocker due to the obscure repro case. I don't see anything in the suspected change that could have caused this so I'm assigning to kenrb@ to triage.

Comment 8 by kenrb@chromium.org, Dec 6 2016

Status: Fixed (was: Assigned)
Closing, since I haven't been able to repro this for some time.
►

Sign in to add a comment