|  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: -
Avg. Score:4.6 ± 0.7
Reproduced:5 of 5 (100.0%)
Same Version:3 (60.0%)
Same OS:1 (20.0%)
From: kael dot shipman at gmail dot com Assigned:
Status: Open Package: FPM related
PHP Version: 5.4.15 OS: Arch Linux
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please — but make sure to vote on the bug!
Your email address:
Solve the problem:
16 + 30 = ?
Subscribe to this entry?

 [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

PHP Copyright © 2001-2021 The PHP Group
All rights reserved.
Last updated: Fri Sep 17 11:03:36 2021 UTC