Bug #14480 Updated: HTML garbaged, server crash

ID: 14480 Updated by: lobbin Reported By: sernil@tin.it Old Status: Open Status: Closed Bug Type: iPlanet related Operating System: HP-UX 11.0, NSAPI PHP Version: 4.0.6 New Comment: Status -> Closed. Previous Comments: ------------------------------------------------------------------------ [2002-01-15 09:08:34] sernil@tin.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 :-( ------------------------------------------------------------------------ [2001-12-17 06:15:32] sernil@tin.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. ------------------------------------------------------------------------ [2001-12-13 21:55:14] sniper@php.net Does this happen with PHP 4.1.0 ? ------------------------------------------------------------------------ [2001-12-13 05:29:08] sernil@tin.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. ------------------------------------------------------------------------ Edit this bug report at http://bugs.php.net/?id=14480&edit=1