566273 - Sufficiently large images displayed incorrectly; cut off after ~32k pixels?

Status: RESOLVED DUPLICATE of bug 567751

(Core :: Graphics: ImageLib, defect)

Description

[Josh Triplett]

Attachment: 6000x50000 grayscale PNG to demonstrate the bug

In doing some data analysis, I needed to work with some images of size
6000x$BIGNUM.  I found that beyond a certain size, Firefox would start
cutting off the bottom of the image.  Judging by the scrollbar position,
32k seems likely, which would make sense.

I've attached a 6000x50000 grayscale PNG, large enough to demonstrate
the problem but still small enough to reasonably attach.  The bright line
in the image should form a smooth curve, but it just stops after a
while.

Note that even larger images seem to hit some internal limit past which
Firefox seems to consider them corrupt and refuses to even display
them, but that seems like a separate bug.

It seemed likely to me that this bug would already exist in Bugzilla, but I didn't manage to find it when I searched; apologies in advance if this ends up a duplicate of some long-standing known bug.

Comment 1

[Mike Hommey [:glandium]]

There is a hardcoded limit, but it is 1000000. Since I know you reported this bug on Debian BTS, would you mind trying to rebuild xulrunner without system libpng support ? (just modify debian/mozconfig.in)

Comment 2

[Boris Zbarsky [:bzbarsky]]

Hmm.  For what it's worth, on trunk (Mac and Linux) I just get a broken-image icon for the attached image.  On Linux 1.9.2 (F12, using the in-tree libpng) I see this bug as reported.

Comment 3

[Boris Zbarsky [:bzbarsky]]

On Mac 1.9.2 I get a broken-image icon.

Comment 4

[Josh Triplett]

(In reply to comment #1)
> There is a hardcoded limit, but it is 1000000.

Hmmmm. I definitely triggered some internal limit in Firefox before that; an image around 1200x300000 didn't display at all, with the same error indication that Firefox gives for a corrupt image file.  But again, different bug.

> Since I know you reported this
> bug on Debian BTS, would you mind trying to rebuild xulrunner without system
> libpng support ? (just modify debian/mozconfig.in)

Will do.

Comment 5

[Josh Triplett]

(In reply to comment #4)
> (In reply to comment #1)
> > There is a hardcoded limit, but it is 1000000.
> 
> Hmmmm. I definitely triggered some internal limit in Firefox before that; an
> image around 1200x300000 didn't display at all, with the same error indication
> that Firefox gives for a corrupt image file.  But again, different bug.

Filed as bug 566453.  (Triggered with a 6000x200000 image.)

> > Since I know you reported this
> > bug on Debian BTS, would you mind trying to rebuild xulrunner without system
> > libpng support ? (just modify debian/mozconfig.in)
> 
> Will do.

Done.  Testing now...

Comment 6

[Josh Triplett]

OK, I've built and installed a new xulrunner with --with-system-png removed, and about:buildconfig confirms that.

The 6000x50000 image still gets cut off at the same point.

Comment 7

[Josh Triplett]

p(i)ng? :)

Comment 8

[Josh Triplett]

With current Firefox 4.0rc1, the 6000x50000 image seems to get treated as corrupt instead, as previously seen with larger images.  See bug 566453.  (However, with that bug fixed this issue may still exist.)

Comment 9

[Ali Juma [:ajuma]]

With Firefox 10, on Windows, Linux, and OS X, the image is treated as corrupt. This matches the behaviour seen in bug 567751, so resolving this as a duplicate. Please feel free to reopen this if it turns out that this bug persists even after bug 567751 is fixed.