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

Issue 760501 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug


Participants' hotlists:
Hotlist-1


Sign in to add a comment

CanvasRenderingContext2D#clip() costs long time

Reported by hyri...@gmail.com, Aug 30 2017

Issue description

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

Example URL:
https://developer.mozilla.org/en-US/docs/Web/API/CanvasRenderingContext2D/clip

Steps to reproduce the problem:
1. goto https://developer.mozilla.org/en-US/docs/Web/API/CanvasRenderingContext2D/clip 
2. at the live example below, edit the code (like adding useless spaces, just want to trigger refreshing)
3. repeat 2. about 10 times

What is the expected behavior?
The page will be stucked for 2~3 seconds.

What went wrong?
Viewing Developer Tools > Performance, it says `ctx.clip()` costs such a long time. While firefox nightly (sorry for I only having this version of firefox) works well.

Does it occur on multiple sites: No

Is it a problem with a plugin? N/A 

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 60.0.3112.113  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 26.0 r0
 
Cc: brajkumar@chromium.org
Components: Blink>Canvas
Labels: -Pri-2 -Type-Compat M-62 hasbisect OS-Linux OS-Mac Pri-1 Type-Bug-Regression
Owner: jinho.b...@samsung.com
Status: Assigned (was: Unconfirmed)
Able to reproduce on Windows 10, Ubuntu 14.04 and Mac OS 10.112.6 using chrome stable M60-60.0.3112.113.

Bisect Information:
---------------------
Good build: 50.0.2648.0
Bad Build : 50.0.2650.0

You are probably looking for a change made after 375291 (known good), but no later than 375300 (first known bad).

Change Log URL: https://chromium.googlesource.com/chromium/src/+log/c4d1f64ab76f833806c877f70885e1738e21f2e7..77fd460b11ab041be48b72d39d6a6b0afc56b4f9

From the above change log suspecting below change
https://chromium.googlesource.com/chromium/src/+/83a374a0cac4710c5af1b5dafc28ae9876d5c721

jinho.bang@ - 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.

Thanks!
Labels: -Pri-1 -Type-Bug-Regression Pri-2 Type-Bug
Owner: ----
Status: Untriaged (was: Assigned)
Not a P1-regression because it regressed in M-50, way back when, and it's not affecting, to our knowledge, a lot of users.

Also marking Untriaged to get some Canvas team eyes on this.

Comment 3 by junov@chromium.org, Oct 2 2017

Owner: jinho.b...@samsung.com
Status: Available (was: Untriaged)
Status: Assigned (was: Available)

Sign in to add a comment