#24542 [Opn->Bgs]: x = func1(func2(x)) does not work

ID: 24542 Updated by: gschlossnagle@php.net Reported By: sysop at kluware dot de -Status: Open +Status: Bogus Bug Type: Reproducible crash Operating System: FreeBSD 4.8 Stable PHP Version: 4.3.2 New Comment: Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://www.php.net/manual/ and the instructions on how to report a bug at http://bugs.php.net/how-to-report.php This is not a bug, simply representative of the different ways that PHP needs to manage temporary variables. At any rate, for handling multiple copies of message bodies that large (as your code does), you memory limit is too low. Previous Comments: ------------------------------------------------------------------------ [2003-07-08 13:20:56] sysop at kluware dot de Description: ------------ We are using IMP/JORDE an our IMAP server. With PHP 4.3.2 (and 4.3.3RC1) we get an error when we try to send very large attachments (> 1.5 MB). IMP aborts with an error like Fatal error: Allowed memory size of 16777216 bytes exhausted at (null):0 (tried to allocate 7565911 bytes) in /var/spool/www/via/phproject/addons/E- Mail/imp/compose.php on line 345 Reproduce code: --------------- When analysing the code at line 345, we found that $contents = chunk_split(base64_encode($contents),76,"\n"); does not realibly work, while $contents1 = base64_encode($contents); $contents = chunk_split($contents1,76,"\n"); doese the job ... Expected result: ---------------- both codelines should have the same result ... Actual result: -------------- 1. Fatal error: Allowed memory size of 16777216 bytes exhausted at (null):0 (tried to allocate 7565911 bytes) in /var/spool/www/via/phproject/addons/E- Mail/imp/compose.php on line 345 2. ok ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=24542&edit=1