ID:               20772
 User updated by:  [EMAIL PROTECTED]
 Reported By:      [EMAIL PROTECTED]
 Status:           Open
 Bug Type:         Filesystem function related
 Operating System: redhat 7.0
 PHP Version:      4.3.0RC2
 New Comment:

I know that "the lack of the memory limit error message is directly
related to bug #20802", I reported bug #20802! ;)

I'm interested to know and the correct the fpassthru problem with this
bug report.


Previous Comments:
------------------------------------------------------------------------

[2002-12-04 18:15:35] [EMAIL PROTECTED]

The lack of the memory limit error message is directly related to bug
#20802.

------------------------------------------------------------------------

[2002-12-03 16:40:09] [EMAIL PROTECTED]

I have changed this bug report to analyze simply the "fpassthru()" bug
and I have opened to other bug reports regarding ob_end_clean and
memory limit problems.

These seem to be independent bugs.

------------------------------------------------------------------------

[2002-12-03 15:38:46] [EMAIL PROTECTED]

Because the problem seems to be a "fpassthru" problem, I have changed
the category from "output control" to "filesystem function"

------------------------------------------------------------------------

[2002-12-03 12:26:57] [EMAIL PROTECTED]

Using php4.3.0RC2:
Now I have put a .htaccess file with
------------------
php_flag output_buffering Off
------------------
and added
ini_set('memory_limit','100M');
at the beginning of the script

and now it works but the script is using 40Mbyte RAM, why?
The
fpassthru($fd)
function seems to load the complete file in memory but in version 4.2.3
it sent it directly to the output without loading it in memory.

------------------------------------------------------------------------

[2002-12-03 06:43:53] [EMAIL PROTECTED]

to add to the summary:

php 4.3.0RC2 without output buffering : "unable to
find the server" error.

------------------------------------------------------------------------

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
    http://bugs.php.net/20772

-- 
Edit this bug report at http://bugs.php.net/?id=20772&edit=1

Reply via email to