Issue metadata
Sign in to add a comment
|
painting on google maps canvas overlay significantly slower on Chrome 61
Reported by
colind...@gmail.com,
Oct 9 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/61.0.3163.100 Chrome/61.0.3163.100 Safari/537.36 Steps to reproduce the problem: Google maps canvas overlays are significantly slower under chrome 61. Developer tools shows that for the attached example, the time to paint "Composite Layers" goes from 0.3 ms under chrome 60 to over 30 ms for chrome 61. 1. Open the attached example in chrome 60 2. Open developer tools, performance tab 3. Start recording, move the mouse, stop recording 4. Repeat with chrome 61 for comparison What is the expected behavior? painting should not be 100 times slower in chrome 61 What went wrong? painting "composite layers" is now roughly 100 times slower. Did this work before? Yes 60 Does this work in other browsers? Yes Chrome version: 61.0.3163.100 Channel: stable OS Version: ubuntu 14.04 Flash Version: I have not yet been able to replicate this problem without using google maps.
,
Oct 10 2017
Could you also try adjusting the window size to see if the slowness is related to the canvas size?
,
Oct 10 2017
It looks to me that you have reproduced the problem. Your screenshot shows 13.9 ms, did you try chrome 60? Reducing the size of the window stops the problem from happening for me, see screenshot. Turning off hardware acceleration makes the problem intermittent, it happens on some frames but not others, see screenshot. My CPU is an i7 860 , 2.8GHz. I have tried a couple of other machines. On a lower-spec windows laptop (smaller screen) I cannot reproduce the problem. On a higher-spec Ubuntu machine I can reproduce the problem but it is intermittent.
,
Oct 10 2017
Thank you for providing more feedback. Adding requester "divya.padigela@techmahindra.com" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 11 2017
It seems the issue has been fixed in latest M62 #62.0.3202.45 and the change log that has fixed the issue seems to be as follows: Change Log: https://chromium.googlesource.com/chromium/src/+log/d51a15f3e2ad328782abc2382e4f6633e3a2ba53..a383490a73bf5dc1d6b996ddf33b62fd3205e0da Blink Change Log: https://skia.googlesource.com/skia.git/+log/abd677455809..8b1360dcfab9 Change-Id: I49fd5ef7968272d311249c3824fe15bee4648b73 Reviewed-on: https://skia-review.googlesource.com/43183 The issue looks similar to issue id: 760738. Hence, merging into issue id: 760738. Thanks...!!
,
Oct 23 2017
The NextAction date has arrived: 2017-10-23 |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by divya.pa...@techmahindra.com
, Oct 10 2017Labels: Triaged-ET Needs-Triage-M61 Needs-Feedback
324 KB
324 KB View Download