|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #40104 Workflow Issue: Object destruction vs Output buffer
Submitted: 2007-01-11 22:42 UTC Modified: 2007-01-12 08:29 UTC
From: denis at mesoconcepts dot com Assigned:
Status: Not a bug Package: Output Control
PHP Version: 5.2.0 OS: all (php related)
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 !
Your email address:
Solve the problem:
23 + 12 = ?
Subscribe to this entry?

 [2007-01-11 22:42 UTC] denis at mesoconcepts dot com
Starting with php 5.2, objects are destroyed before output buffer handlers are called.

Reproduce code:
class foo
  function bar()

$GLOBALS['fb'] =& new foo;

function foo_bar($buffer)
  return $buffer;


Expected result:
The code should not spit an error due to the $fb object not being initialized, as was the case prior to php 5.2.

Actual result:
PHP Fatal error: Call to a member function bar() on a non-object


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2007-01-12 08:29 UTC]
This is the way it works since 5.1.x and we're not going to change it again.
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Sat Jun 22 12:01:30 2024 UTC