Issue metadata
Sign in to add a comment
|
Regression:PDF turns unresponsive when navigating to new tab
Reported by
vineetha...@etouch.net,
Mar 1 2018
|
||||||||||||||||||||||
Issue descriptionChrome Version: 66.0.3358.0 (Official Build) 16fdb6c5f5d6e5779983e253b5f7c8bdd1cac610-refs/heads/master@{#539998}(32/64-bit) OS: Windows (7,8,8.1,10), Linux(14.04 LTS) What steps will reproduce the problem? (1) Freshly launch chrome, navigate to any PDF for e.g : http://cb.vu/unixtoolbox.pdf. (2) Now navigate to any other tab and come back to the PDF and observe that PDF turns unresponsive. (3) Download, rotating pdf etc. icons don't work. Actual Result: PDF turns unresponsive after navigating to a new tab and coming back. Expected Result: PDF should not turn unresponsive after navigating to a new tab. This is a regression issue, broken in M-66 series, Good build: 66.0.3356.0 (Revision: 539381) Bad build: 66.0.3357.0 (Revision: 539659) Unable to provide bisect through per-revision script as chrome builds between #66.0.3356.0 - 66.0.3357.0 are getting crashed while bisecting on Windows (7,8,8.1,10) and Linux(14.04 LTS) OS. Hence, providing Suspect from Narrow bisect, Narrow Bisect: https://chromium.googlesource.com/chromium/src/+log/7514e441317c18910ef6cca47c7967a0b656bdaf..aa432364df013ac6393017c52dde963fb2e1fd4e?pretty=fuller&n=100 suspect: r539639 @fsamuel: 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. Note: Issue is not reproducible for Mac(10.12.6,10.13.1,10.13.4) Thank You!
,
Mar 1 2018
I've reverted the patch. This should be fixed.
,
Mar 1 2018
[Auto-generated comment by a script] We noticed that this issue is targeted for M-66; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-66 label, otherwise remove Merge-TBD label. Thanks.
,
Mar 5 2018
fsamuel@, is revert list at #2 need merge to M66? M66 Branch #3359, branched at chromium revision 540276.
,
Mar 5 2018
The revert landed in time. The fixed reland did not. This fixes another issue for M66: https://chromium-review.googlesource.com/c/chromium/src/+/943725 Could I get a merge for this?
,
Mar 5 2018
Adding "Merge-Request-66" per comment #5.
,
Mar 5 2018
Pls provide M66 merge justification, how safe cl is to merge and why it is needed. Thank you.
,
Mar 5 2018
The context is in https://bugs.chromium.org/p/chromium/issues/detail?id=813157: Content stops redrawing after moving maximized tab to second screen Should I make the request in the other bug? I'm fairly confident it's safe because it's been in canary for a few days without any complaints.
,
Mar 5 2018
Pls request a merge in https://bugs.chromium.org/p/chromium/issues/detail?id=813157. And remove "Merge-Request-66" from this bug if nothing is pending for this bug.
,
Mar 6 2018
Your change meets the bar and is auto-approved for M66. Please go ahead and merge the CL to branch 3359 manually. Please contact milestone owner if you have questions. Owners: cmasso@(Android), cmasso@(iOS), josafat@(ChromeOS), abdulsyed@(Desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 7 2018
Is there anything pending to merge here to M66? If not, pls remove "Merge-Approved-66" label. Thank you.
,
Mar 7 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by nyerramilli@chromium.org
, Mar 1 2018Labels: ReleaseBlock-Stable