ImageLib decodes GIF, JPEG and PNG images, and provides the decoded data to the Compositor for display. If Firefox or Seamonkey can display an image when loaded separately from the page, ImageLib is working, and the actual imaging bug exists elsewhere within Firefox or Seamonkey.

Security

(public)

User Story

If I go to http://www.blizzard.com/broodwar/, the browser grinds to a halt
as the page is loading. When I finally get control back, I see 3 temp files in
the application directory, temp00000001, temp00000002, temp00000003 which range
from about 2Mb to 6Mb in size.
I *think* these temp files are coming from the jpeg library's backing store code
(which uses ANSI temp file stuff), since breaking during the disk grinding shows
jpeg_huff_decode and read_backing_store on the stack.
But it seems very wrong that decoding a few images needs to dump about 10Mb of
data onto the disk.

It still happens. Loading
http://www.blizzard.com/images/broodwar/background2.jpg causes lots of disk
activity, and freezes up my machine for several seconds. I see these files in the
application directory:
temp00000000
temp00000001
temp00000002
It took mozilla almost a minute to render that JPEG.

also experiencing this bug in mac os 9 Mozilla Build ID: 2001112011
when loading a url that contains large images 3 temp files of 324k each are
created in "Mozilla Folder", are labelled temp0000000[A-Z,0-..]