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

Issue 650983 link

Starred by 2 users
Status: Fixed
Owner: ----
Closed: May 2017
Cc:
█ roc...@chromium.org
nyerramilli@chromium.org
enne@chromium.org
█ ranjitkan@chromium.org
mac-bugs-priority@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression : Unable to reload the ‘killed page’ in ‘Browser sample’ app, instead ‘sad face’ is seen on reloading.

Reported by yfulgaon...@etouch.net, Sep 28 2016 
Chrome Version : 54.0.2840.41 (Official Build) aeb8895aa4becddb1526af10d1e67495713b6c1a-refs/branch-heads/2840@{#557} (64-bit)
OS: Mac(10.10.5)(10.11.5)

URL : https://chrome.google.com/webstore/detail/browser-sample/edggnmnajhcbhlnpjnogkjpghaikidaa

What steps will reproduce the problem?
1. Launch chrome and add 'browser sample' app from above mentioned URL.
2. Launch 'browser sample' app and click on ’Simulate crash’ button. (‘Aw snap!’ message is seen)
3. Now click on ‘Reload’ button (seen at the app toolbar) and observe.

Actual : Unable to reload the ‘killed page’ in ‘Browser sample’ app, instead ‘sad face’ is seen on reloading.
Expected : Should be able to reload the ‘killed page’ in ‘Browser sample’ app.

This is a regression issue broken in ‘M-54’, below is the Manual Regression and will soon update bisect info.
Good build : 54.0.2809.0
Bad build : 54.0.2810.0

Note : This is Mac specific issue and not seen on Windows and Linux OS.
Actual_browser_sample.mov
4.6 MB Download
Expected_browser_sample.mov
4.3 MB Download

Comment 1 by yfulgaon...@etouch.net, Sep 28 2016

Owner: eroman@chromium.org
Status: Assigned (was: Unconfirmed)
Narrow Bisect : 
https://chromium.googlesource.com/chromium/src/+log/a86eb14b66aec353ca5f12980f53f5c7935371b5..4a25002ddbb8aece950b4fadefea4a9ac4632ef8?pretty=fuller&n=10000

Suspecting: r408182 ? from Narrow Bisect

@eroman : Please help to re-assign if your change is not the cause for this issue.

Comment 2 by eroman@chromium.org, Sep 28 2016

Owner: ----
Status: Untriaged (was: Assigned)
Thanks for the report.
r408182 should not be related to that.

Assuming the bisect range is correct, I think these are possible candidates to consider given it changes renderer interactions.

https://chromium.googlesource.com/chromium/src/+/1587e33c1578c277af84c700bd213f5743f09f18

https://chromium.googlesource.com/chromium/src/+/d020d554c9ffc0476d43f5364a47c522b64e3d9a

Comment 3 by yfulgaon...@etouch.net, Oct 17 2016

Cc: enne@chromium.org
Owner: roc...@chromium.org
Status: Assigned (was: Untriaged)
Thanks eroman.

Assigning it to 408173, as issue is still reproducible on latest chrome canary 56.0.2891.0

@rockot : Please take a look and help to re-assign if your change is not the cause for this issue. Thank you!

Comment 4 by roc...@chromium.org, May 29 2017

Cc: roc...@chromium.org
Owner: ----
Status: Fixed (was: Assigned)
This appears to have been fixed at some point.
►

Sign in to add a comment