[Tickets #3177] select messages appear blank due to buildmessage exiting.

[bugs@bugs.horde.org]

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

Ticket URL: https://dev.horde.org/horde/whups/ticket/?id=3177
-----------------------------------------------------------------------
 Ticket             | 3177
 Updated By         | phyre at rogers.com
 Summary            | select messages appear blank due to buildmessage exiting.
 Queue              | IMP
 Version            | 4.0.4
 State              | Feedback
 Priority           | 1. Low
 Type               | Bug
 Owners             | 
-----------------------------------------------------------------------


phyre at rogers.com (2005-12-22 10:31) wrote:

No segfaults appear in Apache logs (where they normally go on very rare
occasion when they do happen).  Upgraded to c-client 2004g (the latest) and
still have this problem (was using 2002e (debian)).  

I have figured out the problem.  The problem seems to be a 750KB JPG file
(and in the other e-mail probably a similarly large jpg or bmp file).  I can
create additional jpg files in the 500-800KB range and have the same issue.

My first thought was memory limit, but the memory limit was already at 64MB.
 I have upped it to 80M and now all is well with these messages.  Sorry for
the false alarm here.

This leads to a feature suggestion (as with 5MB digital camera images these
days, this could grow as a problem if a <1MB file fills 80MB).  I imagine
there's some code to create a thumbnail or get image information that is
resulting in the image being decompressed in memory, and the memory is being
exhausted in those cases.  Maybe a configurable option -or- auto-detection
based on the current memory limit as to what is a reasonable image to
decode, and otherwise just leave it intact?

Sorry for the alarm again (though maybe having this here will help another).
 I'd be very curious about that feature request though, as e-mails and
images are only getting bigger.

Cheers,!