Issue metadata
Sign in to add a comment
|
HTML Canvas DrawImage function Very Slow using Not-In-Dom Canvas with HW Acceleration Enabled
Reported by
dat...@gmail.com,
Feb 9 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36 Example URL: https://jsperf.com/canvas-rendering/2 Steps to reproduce the problem: 1. Make sure HW Acceleration is enabled 2. Go to https://jsperf.com/canvas-rendering/2 and run tests 3. Run the test - notice how slow not-in-dom rendering is (mayhangs some computers) What is the expected behavior? 1. Make sure HW Acceleration is disabled (in settings) 2. Go to https://jsperf.com/canvas-rendering/2 and run tests 3. Notice the tests complete (with reasonable results) What went wrong? Google Chrome has a bug with HW acceleration and not-in-dom canvas when using drawimage function in javascript. Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? Yes Chrome 63 Does this work in other browsers? Yes Chrome version: 64.0.3282.140 Channel: stable OS Version: 10.0 Flash Version: Was a problem in Chrome 63 but is much, much worse in Chrome 64
,
Feb 9 2018
,
Feb 9 2018
,
Feb 10 2018
,
Feb 10 2018
Tested with Version 65.0.3325.51 (Official Build) beta (64-bit). Issues is NOT resolved.
,
Feb 10 2018
Tested with Version 66.0.3344.0 (Official Build) canary (64-bit). Issues is NOT resolved.
,
Feb 12 2018
Issue 810689 has been merged into this issue.
,
Feb 12 2018
Tested the issue on Win-10 using chrome reported version #64.0.3282.140 and latest canary #66.0.3344.0. Attached screen casts for reference. Following are the steps followed to reproduce the issue. ------------ 1. Made sure HW Acceleration is enabled 2. Navigated to https://jsperf.com/canvas-rendering/2 and ran tests 3. Observed that on both enabling/disabling the hardware acceleration, there is slow not-in-dom rendering. No much difference is observed. datnow@ - Could you please check the attached screencast and please let us know if anything missed from our side. Also if possible please provide any other alternate url to triage the issue from our end. A screencast will be more helpful. Thanks...!!
,
Feb 12 2018
Thank you for providing more feedback. Adding requester "krajshree@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
,
Feb 13 2018
datnow@ - Thanks for the screencasts at comment #9. Could you please provide a sample url as shown in the attached screen casts to triage the issue from TE-end. Thanks...!!
,
Feb 13 2018
,
Feb 13 2018
This has been fixed. Fix will be available in the next Chrome 64 update. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by dat...@gmail.com
, Feb 9 2018