|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
[2002-10-24 02:42 UTC] sniper@php.net
[2002-10-24 04:27 UTC] kamil at kamil dot eisp dot pl
[2002-10-24 12:26 UTC] sniper@php.net
[2002-12-03 01:12 UTC] shane@php.net
|
|||||||||||||||||||||||||||||||||||||
Copyright © 2001-2025 The PHP GroupAll rights reserved. |
Last updated: Wed Nov 26 11:00:02 2025 UTC |
Under very specific circumstances, php goes in tight infinite loop eating all cpu after request is cancelled. Configuration: php 4.2.3 as cgi apache 1.3.27 php configured with Action directive, (important) using suexec. Conditions for problem to occur in script: 1.ignore_user_abort(true) 2.sending any http header 3.sending any body content AFTER http header 4. connection is aborted before all data are sent to client. Script to reproduce problem: ---- CUT ---- <? ignore_user_abort(true); header("X-Whatever: whatever"); ?> whatever ---- CUT ---- Problem doesn't exist with mod_php or php-cgi without suexec. It appears that after apache has closed connection php is still trying to write output and loops for unknown reason. I'm not sure if this is fault of php, apache or suexec, but I think it could be fixed in php.