Issue metadata
Sign in to add a comment
|
Graphics crash when drawing specific (large) image to canvas in 2d context
Reported by
tarvorei...@gmail.com,
Oct 6 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36 Steps to reproduce the problem: To make things easier on myself, I will use someone else's JSFiddle, whose code can reproduce the issue. 1: Visit the following JSFiddle: https://jsfiddle.net/7nyaoaff/2/ 2: Use the following image: http://filecache.drivetheweb.com/mr5mr_boeing/91092/MAX-LEAP2-low.jpg What is the expected behavior? The image should be resized properly. What went wrong? On my setup, all Chrome windows go black and the rendered image will be blank. On my co-worker's setup, the resulting image was blank, but the Chrome windows did not flicker. Did this work before? N/A Chrome version: 53.0.2785.143 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 23.0 r0
,
Oct 6 2016
Tested it on my personal computer and it did not happen. How would I be able to receive the logs for the graphics crash?
,
Oct 12 2016
Can you please provide chrome://gpu information and crash id from chrome://crashes.
,
Oct 13 2016
Unable to reproduce the issue on the reported version(53.0.2785.143) on Windows-10. Attached is the gpu details of the system this was tested on. tarvoreinpalu@: Please update the thread as per C#3.
,
Oct 13 2016
Attached GPU info. This does not appear under 'crashes', because the browser itself doesn't crash. Only the rendering on one tab dies for up to 10 seconds before it recovers. It recovers enough to render the content, but the canvas resize, that was requested in the code, fails. Also attached my co-workers GPU info. His resize fails, but the screen doesn't flicker as it does for me. In his case, the result is a blank canvas.
,
Oct 13 2016
Adding plain text versions of the logs.
,
Oct 13 2016
We recently made changes to how large images are handled. This should have fixed the problem. Could you try using the latest Canary build of Chrome to tell us whether you still experience the problem there? https://www.google.com/chrome/browser/canary.html
,
Oct 13 2016
,
Oct 13 2016
The issue is not present on the Canary build of Chrome. Cool beans.
,
Oct 13 2016
\o/ Closing issue |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by tarvorei...@gmail.com
, Oct 6 2016