[Tickets #5315] Re: Horde_Image_gd code hits memory limit on large images

[bugs at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=5315
-----------------------------------------------------------------------
 Ticket             | 5315
 Updated By         | Jan Schneider <jan at horde.org>
 Summary            | Horde_Image_gd code hits memory limit on large images
 Queue              | Horde Framework Packages
 Version            | HEAD
 Type               | Bug
 State              | Feedback
 Priority           | 1. Low
 Owners             | 
-----------------------------------------------------------------------


Jan Schneider <jan at horde.org> (2007-05-02 01:25) wrote:

> However when I tried to open the same image in IrfanView it consumed 
> ~104Mb. Does this mean that most email programs (including GD 
> library) just loads raw code into memory without any optimizations? I 

Not only email programs I guess. Image viewers are usually optimized to
display any kind of image, of any size.

> wonder what could be done in such cases. Try to hack GD library to 
> limit picture size?

I don't know if this is possible. Ask Pierre who is maintaining the GD
library for the PHP project now.

> P.S. I also noticed that _getHordeImageObj() is called twice for 
> every image attachment. Could this also be the problem?

This could at least make it worse. I tweaked the code so that at least the
image data is not loaded in IMP_MIME_Viewer_images::_getHordeImageObj() if
not necessary. See if this helps any.