Correct link:

https://groups.google.com/a/chromium.org/forum/#!topic/chromium-discuss/3Yn_fy985Mc

palomathedoveborn@ Thanks for the issue.

Tested this issue on MacBook Pro OS 10.13.1 with Retina display on the reported version 65.0.3325.162 and the latest Canary 67.0.3376.1 by following the below steps.

1. Launched Chrome with Hardware Acceleration Enabled and navigated to the link given in the original comment.
2. Navigated to the link http://poe.rivsoft.net/ and enabled FPS meter in Devtools -> Console -> Rendering.
3. On hovering the mouse, can observe the FPS ~20.
The same behavior is observed when the Hardware Acceleration is Disabled.
Attached is the screen cast for request.

Request you to check and confirm if these are the right steps in reproducing the issue, which will help in further triaging.

Thanks...

Deleted: 823335.mp4 4.3 MB

	823335.mp4 4.3 MB View Download

I have had people try to replicate it but with no success. I think it may be an issue with my OSX being old (10.11.6). I attach a video of what I experience with the canvas example at https://al-ro.github.io/projects/heart/

Deleted: diff.mov 8.2 MB

	diff.mov 8.2 MB View Download

Thank you for providing more feedback. Adding the requester to the cc list.

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

palomathedoveborn@ Thanks for the feedback.

As per comment #4, the issue can be reproduced on Mac OS 10.11.6. 
As Mac OS 10.11.6 is unavailable at TE end to test this issue, adding 'TE-NeedsTriageFromMTV' label and requesting someone from MTV team to look into this issue and help in further triaging.

Thanks..

We've just seen this same issue with our Canvas app and after some troubleshooting believe it may have to do with El Capitan (OSX 10.11.6) and the latest Chrome version (65.0.3325.181) not playing well together. Echoing Comment 4.

With High Sierra (OSX 10.13.3) and the same Chrome version (65.0.3325.181), canvas/HTML5 rendering with hardware acceleration ON render performance does not appear to be impacted, or at least not as severely.

Overall it is a pretty crippling issue and hopefully the Chrome folks can take a look ASAP. Thanks!

 Issue 824668  has been merged into this issue.

 Issue 824725  has been merged into this issue.

Issue 822417 is potentially a duplicate? https://bugs.chromium.org/p/chromium/issues/detail?id=822417

For the record, I'm also on El Capitan (OSX 10.11.6) and am seeing the same sluggish canvas performance.

Also affecting users of https://www.piskelapp.com (a web based sprite editor) as confirmed on https://github.com/piskelapp/piskel/issues/796

Apparently makes the website completely unusable for users with OSX 10.11.6

(edit: reposted comment to fix incorrect link)

This is also affecting users of http://p5js.org/ as seen in this issue: https://github.com/processing/p5.js/issues/2769

Is it related with https://bugs.chromium.org/p/chromium/issues/detail?id=794819?

vamshi.kommuri@ Please image one of the test machines with Mac 10.11 and retriage.

cc'ing folks on related bug. Seems plausible that very broad GPU blacklisting caused a large perf regression. Can the change in skia that exposed the driver bug be dealt with instead?

M67 Beta promotion is coming VERY soon. Pls make sure to land the fix and request a merge into the release branch ASAP. Thank you.

ccameron@: Could you take a look? Any ideas?

This issue was originally reported on M65, so exists on M66 and M67. Don't think this should be a beta blocker for M67. Pls let me know if I'm missing anything here.

Please post the contents of about:gpu from an affected machine. It seems likely this is the same problem as  Issue 773705 , where GPU acceleration for 2D canvas had to be disabled because of bugs in Apple's graphics driver for NVIDIA GPUs in 10.13 (apparently fixed in 10.13.4, and re-enabled in Chrome from that release on).

I bet that this is a duplicate of  issue 791828 .

We blacklisted LOTS of GPUs gpu-raster and gpu-canvas in 65, and there are performance potholes in the non-accelerated path.

This is also being reported on 10.11, and I'm not re-enabling GPU-anything there (just 10.13.4). But hopefully Kushal's patch can be merged to 67 and will fix this (testing it locally now).

M67 Beta promotion is coming VERY soon. Your bug is labelled as Beta  ReleaseBlock, pls make sure to land the fix and request a merge into the release branch latest by 1:00 PM PT Friday, 04/20.  Thank you.

Fix should land tonight, hopefully.

Ok, great. Thank you. Pls request a merge to M67 once change is baked in canary. 

Just checking back, is the change landed in trunk last night?

Duplicating to  issue 773705 , which is the root cause (fix in the CQ).

... I mean  issue 791828 .