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

Issue 721727 link

Starred by 6 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Jul 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug



Sign in to add a comment

chrome 58 canvas draw bug

Reported by gengc...@126.com, May 12 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36

Steps to reproduce the problem:
1. Using canvas to draw maps, canvas multiple
2. Some of the maps displayed by canvas will be deranged
3. Only problems occurred on version chrome 58
4.Switching chrome page labels is confused and canvas changes back and forth

What is the expected behavior?
map Canvas normal display

What went wrong?
Some of the maps displayed by canvas will be deranged

Did this work before? N/A 

Chrome version: 58.0.3029.110  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:
 
chrome-canvas-bug.html
948 bytes View Download
Labels: Needs-Triage-M58
Cc: kkaluri@chromium.org
Labels: Needs-Feedback
gengcjun@ Could you please confirm the below are the screenshots are the actual and expected behavior of this issue. 
Issue 721727 - Expected.png
171 KB View Download
Issue 721727 - Actual.png
167 KB View Download

Comment 3 by gengc...@126.com, May 16 2017

yes, Actual.png is Deranged canvas,I don't know what caused it,The previous version was good
Project Member

Comment 4 by sheriffbot@chromium.org, May 16 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Comment 5 by gengc...@126.com, May 16 2017

Want to know that this confirmation is chrome's bug, and then split it, right?

Comment 6 by gengc...@126.com, May 16 2017

I'm calling an online product, and the bug is currently running an emergency line. Do I need to get a new bug page again?

Comment 7 by bokan@chromium.org, May 16 2017

Components: -Blink Blink>Canvas

Comment 8 by gengc...@126.com, May 17 2017

Do I need to provide a test address?
Cc: kavvaru@chromium.org
Labels: Needs-Feedback
Unable to reproduce the issue on windows 7, Mac 10.12.4 using chrome version 58.0.3029.110 and canary 60.0.3100.0 with the below steps

1.Opened the attached html file on chrome
2.Displayed empty page
3.If move the zoom bar then it is displaying the canavas
4.Not observed any Deranged canvas

Please find the attached screen cast and confirm if anything missed here.
But the same displayed fine on Firefox without zoom.
Please provide us any other sample case to triage the issue consistently.

Thanks,
721727.mp4
803 KB View Download
Project Member

Comment 11 by sheriffbot@chromium.org, May 17 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "kavvaru@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Comment 12 by gengc...@126.com, May 17 2017

I recorded a video,Canvas has been messy
EV~2017.05.17~20.3413.mp4
2.4 MB View Download
Cc: krajshree@chromium.org
Unable to reproduce the issue on Win-7 and Win-10 using chrome reported version #58.0.3029.110 and latest canary #60.0.3103.0.

Attached a screen cast for reference.

Following are the steps followed to reproduce the issue.
------------
1. Navigated to URL: http://3gimg.qq.com/jiejingweb/TPanoVideo/chrome/chrome-canvas-bug.html
2. Observed that map canvas displayed normally as expected.

Could anyone from Blink>Canvas team please have a look into this issue.

Thanks...!!
721727.mp4
5.0 MB View Download
I think that this bug is related to bug that I reported: https://bugs.chromium.org/p/chromium/issues/detail?id=724864

I am able to reproduce it using Intel Graphics 530 and problem disappers when switch to Nvidia (change options for chrome in NVIDIA Control Panel).

In my bug report I attached very simple test.

Comment 15 by gengc...@126.com, May 22 2017

yes I looked at my bug and yours should be one
Cc: hdodda@chromium.org
 Issue 724864  has been merged into this issue.
Labels: TE-NeedsTriageFromMTV
As per comment#14, this issue specific to Intel Graphics 530.

As inhouse-team doesn't have Intel graphics 530 ,could someone from MTV Team to please look into this issue.

Thanks!
Components: -Blink>Canvas Internals>GPU>VendorSpecific

Comment 19 by gengc...@126.com, May 24 2017

I was good before upgrading chrome58,
There are also many people, this situation should be a universal phenomenon
EV~2017.05.22~18.1239.mp4
1.7 MB View Download
Cc: vmi...@chromium.org jbau...@chromium.org
Labels: Needs-Feedback
Can folks affected by this bug please post the contents of the chrome://gpu page pasted into a text file, please? We're trying to determine if this is an issue caused by Chrome or by an Intel/Nvidia driver update or a Windows update. Also it would be great if you could test an older version of Chromium: https://www.googleapis.com/download/storage/v1/b/chromium-browser-snapshots/o/Win%2F444943%2Fchrome-win32.zip?generation=1484879768408272&alt=media and see if the bug reproduces?

Comment 21 by gengc...@126.com, May 26 2017

chrome 57 version is good,only 58 verison is error
chrome-gpu.txt
11.8 KB View Download
Project Member

Comment 22 by sheriffbot@chromium.org, May 26 2017

Cc: sunn...@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "sunnyps@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
I can reproduce bug on chrome 57 with example canvasArtifactsBug.html. I can't check http://3gimg.qq.com/jiejingweb/TPanoVideo/chrome/chrome-canvas-bug.html because it is not working at the moment.

chrome-gpu.txt
14.2 KB View Download

Comment 24 by enne@chromium.org, Jun 2 2017

Owner: junov@chromium.org
Status: Assigned (was: Unconfirmed)
junov: sounds like this is a regression in m58, could you investigate?
hi, 

I have the same bug on the "waves" of this website (multiple html5 canvas) :

http://bit.ly/2lrcWiV

the effect was ok in chrome 57 ; bug in chrome 58.

Comment 26 by junov@chromium.org, Jun 14 2017

Components: Internals>GPU>ANGLE
Labels: Needs-Bisect
Owner: ----
Status: Available (was: Assigned)
I am unable to investigate this because I don't have access to any hardware that reproduces the problem.  I need at least a narrow bisect as a starting point. 

From the screenshots it looks like the textures are getting mismatched
Since this is windows-only, could be a bug in ANGLE.

Comment 27 by junov@chromium.org, Jun 15 2017

Cc: junov@chromium.org
 Issue 724435  has been merged into this issue.
I've updated to chrome 59.0.3071.115 and the problem persists. Also I don't think it's a windows-only problem. I've a report from an user using OSX.

This bug is getting really annoying as we have received a lots of complains.
Labels: -Pri-2 Pri-1
Components: Blink>Canvas
Useful info from duplicate  bug 724435  : problem goes away when you disable the display-list-2d-canvas option on the chrome://flags page.

If we continue to be unable repro/investigate this bug in house, we may simply change the "display-list-2d-canvas" option to make it disabled by default.  All of you who are experiencing this issue: can you confirm that disabling this option makes the bug go away?
Yes, disabling display-list-2d-canvas solve the problem.
Yes, I also confirm.

Comment 34 Deleted

Comment 35 Deleted

Comment 36 by gengc...@126.com, Jul 7 2017

Yes, disabling display-list-2d-canvas solve the problem. bug, It's impossible for users to do this change themselves, or have to solve the problem at the root
> It's impossible for users to do this change themselves

Agreed. We may take care of the issue by disabling the option by default in an update of Chrome. I just wanted to know whether this flag solved the issue for everyone.


Comment 38 by gengc...@126.com, Jul 10 2017

good,expect problems to be solved in the new release
Project Member

Comment 39 by bugdroid1@chromium.org, Jul 10 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/3750a7881ce851e03ce6177dca30307eb4a7f5c6

commit 3750a7881ce851e03ce6177dca30307eb4a7f5c6
Author: Justin Novosad <junov@chromium.org>
Date: Mon Jul 10 20:50:59 2017

Disabling display list 2D canvas by default

As a temporary fix for  bug 721727 , we are disabling display list 2D
canvas by default.  With this change, display list mode is only engaged
when specifying the --force-display-list-2d-canvas command line option.

BUG= 721727 

TBR=zmo@chromium.org

Change-Id: I26f0caa3b62506c8d2d051bec208a94c1f51341f
Reviewed-on: https://chromium-review.googlesource.com/563519
Reviewed-by: Justin Novosad <junov@chromium.org>
Reviewed-by: Fernando Serboncini <fserb@chromium.org>
Commit-Queue: Justin Novosad <junov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#485371}
[modify] https://crrev.com/3750a7881ce851e03ce6177dca30307eb4a7f5c6/content/test/gpu/gpu_tests/pixel_expectations.py
[modify] https://crrev.com/3750a7881ce851e03ce6177dca30307eb4a7f5c6/third_party/WebKit/Source/core/html/HTMLCanvasElement.cpp

Comment 40 by gengc...@126.com, Jul 11 2017

ok thanks What version will be released for this change?

Comment 41 by junov@chromium.org, Jul 11 2017

Labels: Merge-Request-60
@#40 Currently, the fix is in the Chromium trunk, which means Chrome 61.
You can verify the fix by installing the Chrome Canary (nightly build).  This takes only a few minutes and does not require uninstalling your regular Chrome.  Get it here: https://www.google.com/chrome/browser/canary.html

Since this bug harshly impacts several production web sites, I am requesting permission to merge the fix to the Chrome 60 branch so we can get it out sooner.
Project Member

Comment 42 by sheriffbot@chromium.org, Jul 11 2017

Labels: -Merge-Request-60 Hotlist-Merge-Review Merge-Review-60
This bug requires manual review: We are only 13 days from stable.
Please contact the milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), josafat@(ChromeOS), bustamante@(Desktop)

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

Comment 43 by junov@chromium.org, Jul 11 2017

To milestone owners: The fix has very low risk. It is a one line code change that disables a code path that regressed recently in favor of always using a mature and stable code path that has been in production for years.
Labels: -Merge-Review-60 Merge-Approved-60
If this fix has been tested in Canary and is considered a safe merge (as confirmed in comment 41 and 43), approving merge to M60. Branch: 3112. 
Project Member

Comment 45 by bugdroid1@chromium.org, Jul 13 2017

Labels: -merge-approved-60 merge-merged-3112
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/595a4a428ac15b0ab61deaf3dbc309867c11eb3a

commit 595a4a428ac15b0ab61deaf3dbc309867c11eb3a
Author: Justin Novosad <junov@chromium.org>
Date: Thu Jul 13 19:41:38 2017

Disabling display list 2D canvas by default

As a temporary fix for  bug 721727 , we are disabling display list 2D
canvas by default.  With this change, display list mode is only engaged
when specifying the --force-display-list-2d-canvas command line option.

BUG= 721727 

TBR=junov@chromium.org, zmo@chromium.org

(cherry picked from commit 3750a7881ce851e03ce6177dca30307eb4a7f5c6)

Change-Id: I26f0caa3b62506c8d2d051bec208a94c1f51341f
Reviewed-on: https://chromium-review.googlesource.com/563519
Reviewed-by: Justin Novosad <junov@chromium.org>
Reviewed-by: Fernando Serboncini <fserb@chromium.org>
Commit-Queue: Justin Novosad <junov@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#485371}
Reviewed-on: https://chromium-review.googlesource.com/570825
Cr-Commit-Position: refs/branch-heads/3112@{#606}
Cr-Branched-From: b6460e24cf59f429d69de255538d0fc7a425ccf9-refs/heads/master@{#474897}
[modify] https://crrev.com/595a4a428ac15b0ab61deaf3dbc309867c11eb3a/content/test/gpu/gpu_tests/pixel_expectations.py
[modify] https://crrev.com/595a4a428ac15b0ab61deaf3dbc309867c11eb3a/third_party/WebKit/Source/core/html/HTMLCanvasElement.cpp

Owner: junov@chromium.org
Status: Assigned (was: Available)

Comment 47 by junov@chromium.org, Jul 25 2017

Closing this bug since there is nothing more to do. Chrome 60 (which has the fix) will be released to the stable channel in just a few days.

Comment 48 by junov@chromium.org, Jul 31 2017

Status: Fixed (was: Assigned)
Project Member

Comment 49 by bugdroid1@chromium.org, Aug 23 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/5f0a7fa2b08349306dd1f7cc0e039b73c14d259a

commit 5f0a7fa2b08349306dd1f7cc0e039b73c14d259a
Author: Justin Novosad <junov@chromium.org>
Date: Wed Aug 23 21:51:30 2017

Clean-up forgotten reference images for gpu pixel tests

Several tests were marked for rebaselining a while ago and seem to
have been forgotten (associated bugs closed).

BUG= 615325 ,  721727 ,  713632 

TBR=dongseong.hwang@intel.com, zakerinasab@chromium.org, vmiura@chromium.org

Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: I0cc24618c7a4647a64ec3ed56318aee18dc9ea72
Reviewed-on: https://chromium-review.googlesource.com/624522
Commit-Queue: Justin Novosad <junov@chromium.org>
Reviewed-by: Mohammad Reza Zakerinasab <zakerinasab@chromium.org>
Reviewed-by: Justin Novosad <junov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#496820}
[modify] https://crrev.com/5f0a7fa2b08349306dd1f7cc0e039b73c14d259a/content/test/gpu/gpu_tests/pixel_expectations.py
[modify] https://crrev.com/5f0a7fa2b08349306dd1f7cc0e039b73c14d259a/content/test/gpu/gpu_tests/pixel_test_pages.py

Project Member

Comment 50 by bugdroid1@chromium.org, Aug 24 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/67358de6affcf94f9cbf3efa1106df5fdbd70549

commit 67358de6affcf94f9cbf3efa1106df5fdbd70549
Author: Justin Novosad <junov@chromium.org>
Date: Thu Aug 24 15:03:09 2017

Rebaseline Pixel_CSSFilterEffects test results

BUG= 721727 
TBR=zmo@chromium.org

Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: I554afcdb96dbeeddefd783308d19d49159e4e772
Reviewed-on: https://chromium-review.googlesource.com/632496
Commit-Queue: Justin Novosad <junov@chromium.org>
Reviewed-by: Justin Novosad <junov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#497048}
[modify] https://crrev.com/67358de6affcf94f9cbf3efa1106df5fdbd70549/content/test/gpu/gpu_tests/pixel_expectations.py

Sign in to add a comment