|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #64956 FPM child processes stop responding after fatal script error
Submitted: 2013-06-01 16:20 UTC Modified: 2021-12-08 22:08 UTC
Avg. Score:4.7 ± 0.7
Reproduced:6 of 6 (100.0%)
Same Version:3 (50.0%)
Same OS:1 (16.7%)
From: kael dot shipman at gmail dot com Assigned: bukka (profile)
Status: Closed Package: FPM related
PHP Version: 5.4.15 OS: Arch Linux
Private report: No CVE-ID: None
 [2013-06-01 16:20 UTC] kael dot shipman at gmail dot com
When php encounters a FATAL error and output buffering is ON, the child process that handled the script no longer outputs anything, even on subsequent requests to working scripts. If the below script is run, it returns a completely blank page. If a non-erred script is then run, the non-erred script also returns a blank page. It's only fixed by killing the offending child process. With output buffering disabled, everything works as expected and the child process doesn't need to be killed.

Test script:
echo "Working happily";

Expected result:
Working happily
FATAL ERROR: Call to undefined function call_nonexistent_function() in.....

Actual result:
Blank page - nothing at all.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2021-12-08 22:08 UTC]
-Status: Open +Status: Closed -Assigned To: +Assigned To: bukka
 [2021-12-08 22:08 UTC]
I think this should be addressed by the changes that went to PHP 7.4 related to signal handling.

Please open a new bug report or comment here if you still see the issue in the latest PHP version.
PHP Copyright © 2001-2023 The PHP Group
All rights reserved.
Last updated: Wed Feb 08 01:03:53 2023 UTC