171972 2017-05-11 06:15:10 -0700 [GTK] Tests fast/images/async-image-background-image-repeated.html and fast/images/sprite-sheet-image-draw.html fail since r216450 2017-08-14 02:45:53 -0700 1 1 1 Unclassified WebKit WebKitGTK WebKit Nightly Build Unspecified Unspecified RESOLVED DUPLICATE 174459 Gtk, LayoutTestFailure P2 Normal --- 1 cgarcia webkit-unassigned bugs-noreply magomez Ms2ger sabouhallawa yoon oldest_to_newest 1307248 0 cgarcia 2017-05-11 06:15:10 -0700 The problem is the change in sprite-sheet-red-green-blue.png. We now fail to render that png, I don't know why. I've tried with other programs: - Firefox shows an error message saying the png has errors - eog crashes with BadAlloc X error. - chromium and gimp render the png just fine - gdk-pixbuf also fails to render it. 1307250 1 cgarcia 2017-05-11 06:21:40 -0700 Tried eog in wayland and we get this warning: (eog:12294): Gtk-WARNING **: drawing failure for widget 'GtkDrawingArea': invalid value (typically too big) for the size of the input (surface, pattern, etc.) So, maybe this is another cairo limitation, and we can't create an image surface for the size of the png. 1307252 2 cgarcia 2017-05-11 06:25:44 -0700 Exactly: /* Limit on the width / height of an image surface in pixels. This is * mainly determined by coordinates of things sent to pixman at the * moment being in 16.16 format. */ #define MAX_IMAGE_SIZE 32767 Said, would it be possible to test the same thing with a png <= 32766 instead of 33100? 1307255 3 cgarcia 2017-05-11 06:33:26 -0700 Expectations updated in r216676. 1309076 4 cgarcia 2017-05-16 02:01:54 -0700 (In reply to Carlos Garcia Campos from comment #2) > Exactly: > > /* Limit on the width / height of an image surface in pixels. This is > > * mainly determined by coordinates of things sent to pixman at the > > * moment being in 16.16 format. */ > #define MAX_IMAGE_SIZE 32767 > > Said, would it be possible to test the same thing with a png <= 32766 > instead of 33100? Said? 1338300 5 Ms2ger 2017-08-14 02:45:53 -0700 *** This bug has been marked as a duplicate of bug 174459 ***