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

Issue 861784 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 859400
Owner:
Closed: Dec 18
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 3
Type: Bug-Regression

Blocked on:
issue 575305



Sign in to add a comment

Canvas rendering fails when canvas width is over 32767 pixels

Reported by lam.wai...@gmail.com, Jul 9

Issue description

Chrome Version       : 67.0.3396.99
URLs (if applicable) : https://jsfiddle.net/wj2pebm0/16/
Other browsers tested:
    Safari:  OK 9.1.2 (11601.7.7)
    Firefox: FAIL 61.0.1
    Edge:    OK 40.15063.674.0

What steps will reproduce the problem?
(1) Create a canvas with width over 32767 pixels wide
(2) Attempt any draw in it (e.g fillRect)

What is the expected result?
Canvas should render the attempt to draw.

What happens instead?
Canvas fails to render entirely.

Please provide any additional information below. Attach a screenshot if
possible.
I've condensed the issue into a JSFiddle: https://jsfiddle.net/wj2pebm0/16/
I've also attached an image.
 
Screen Shot 2018-07-09 at 12.01.02 PM.png
352 KB View Download
Components: Blink>Canvas
Labels: Needs-Triage-M67
Labels: -Type-Bug -Pri-3 hasbisect-per-revision ReleaseBlock-Stable M-68 M-69 M-67 FoundIn-67 RegressedIn-67 Target-69 Triaged-ET FoundIn-69 FoundIn-68 OS-Linux OS-Mac OS-Windows Pri-1 Type-Bug-Regression
Owner: kbr@chromium.org
Able to reproduce issue on reported chrome version 67.0.3396.99 & on latest chrome 69.0.3486.0 using Windows 10,Ubuntu 14.04 and Mac 10.13.5. Hence providing bisect information below.

Bisect Info:
================
Good build: 67.0.3395.0
Bad build: 67.0.3396.0

CHANGELOG URL:
https://chromium.googlesource.com/chromium/src/+log/5f8a9f95b29d079c62ad37be39c3314c5bc899a7..954ed9ceb26067a267165e440bd863f74820ddef

suspect: https://chromium.googlesource.com/chromium/src/+/954ed9ceb26067a267165e440bd863f74820ddef

Reviewed-on: https://chromium-review.googlesource.com/522938

@Kenneth: Please confirm the issue and help in re-assigning if it is not related to your change.

Adding 'ReleaseBlock-Stable' label as this is a recent regression. Please feel free to remove if this is not applicable.

Thanks!
Cc: abdulsyed@chromium.org manoranj...@chromium.org
Labels: -M-67 Target-68
We're not planning any further M67 releases. Pls target fix for M68.
Cc: phanindra.mandapaka@chromium.org
Status: Assigned (was: Unconfirmed)
Blockedon: 575305
Investigating.

Cc: fs...@chromium.org
Labels: -Pri-1 -ReleaseBlock-Stable Pri-3
The fact that the user's intended content didn't show up wasn't changed by https://chromium-review.googlesource.com/522938 . The attempted creation of the 2D canvas context silently failed, and that's why the black dot in the JSFiddle wasn't showing up.

Now the failure to create the 2D canvas context is more visible; the "sad canvas" icon is drawn in its place.

I don't know whether Chrome's behavior is in violation of any HTML specification but regardless this is not a P1 regression nor Release-Block-Stable. Downgrading to P3 and CC'ing fserb@ (overall canvas TL) for any comment.

Components: Internals>Skia
Adding the skia componenent to this issue since it is caused by a limitation of skia.
Cc: kbr@chromium.org
Mergedinto: 859400
Owner: jdarpinian@chromium.org
Status: Duplicate (was: Assigned)
James raised this limit in  Issue 859400  and this sample is now rendering correctly in Chrome Canary.

Sign in to add a comment