|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #14480 HTML garbaged, server crash
Submitted: 2001-12-13 05:29 UTC Modified: 2002-01-15 09:41 UTC
From: sernil at tin dot it Assigned:
Status: Closed Package: iPlanet related
PHP Version: 4.0.6 OS: HP-UX 11.0, NSAPI
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
Block user comment
Status: Assign to:
Bug Type:
From: sernil at tin dot it
New email:
PHP Version: OS:


 [2001-12-13 05:29 UTC] sernil at tin dot it
This is an intermittent bug. Some pages will appear OK
if the HTML is dumped to file just before output using
ob_get_contents(). Yet sections of the same HTML code,
once on the browser, appear to have been replaced with
garbage (apparently sections of the server memory).

Simpler PHP code is not affected.

Occasionally, the CPU load will skyrocket, and the Web
server will crash without returning any data.

I think it could be the PHP module, somehow corrupting
ns-httpd memory, but am unable to investigate further.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2001-12-13 21:55 UTC]
Does this happen with PHP 4.1.0 ?

 [2001-12-17 06:15 UTC] sernil at tin dot it
I'm now installing PHP 4.1.0 and will test under different
load conditions. I expect to be able to tell you something
about 4.1.0 soon after Christmas.
 [2002-01-15 09:08 UTC] sernil at tin dot it
Bug disappeared with PHP 4.1.1 (4.1.0 was not installed).

I'm not really convinced it was PHP, anyway. Before I had
installed 4.1.1, I tried reloading HTML from file without
re-generating it, and re-submitting it to the web server,
and I got the same results (CPU load with crashes).

Unless it's something having to do with the communication
interface between PHP and iPlanet. But is it likely?

Meanwhile, if somebody can't or doesn't want to upgrade, a
possible solution is to dump everything in a file, issue a
ob_end_clean to discard the output, then send a "Location"
header with the URL of the newly created file. You need to
generate unique filenames on a per-client basis, since any
attempt to store them somewhere else and resupply them via
PHP will yield the same crashes :-(
 [2002-01-15 09:41 UTC]
Status -> Closed.
PHP Copyright © 2001-2023 The PHP Group
All rights reserved.
Last updated: Mon Jun 05 20:03:39 2023 UTC