|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #62412 Fixing segfault due to destruction order
Submitted: 2012-06-25 19:33 UTC Modified: 2012-07-18 09:13 UTC
From: Assigned: pdezwart (profile)
Status: Closed Package: amqp (PECL)
PHP Version: 5.3.14 OS:
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:
19 + 35 = ?
Subscribe to this entry?

 [2012-06-25 19:33 UTC]
PHP does not guarantee any destruction order. This means if you instantiate class 
A before B, A may be destructed before B or B may be destructed before A. As 
AMQPChannel needs an AMQPConnection object for construction one could assume, 
that AMQPChannel objects are always destructed before AMQPConnection objects are 
destructed. This may not always be the case. For cases where the AMQPConnection 
object is destructed before the related AMQPChannel the AMQPConnection destructor 
needs to take care of destructing related AMQPChannel objects. And this is what 
the attached patch does.


destruction-order (last revision 2012-06-25 19:34 UTC by lars at strojny dot net)

Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2012-07-08 09:33 UTC]
-Assigned To: +Assigned To: pdezwart
 [2012-07-17 05:19 UTC]
Automatic comment from SVN on behalf of pdezwart
Log: Fixing Bug#62412 destruction order
 [2012-07-18 09:13 UTC]
-Status: Assigned +Status: Closed
 [2012-07-18 09:13 UTC]
Thank you for your bug report. This issue has already been fixed
in the latest released version of PHP, which you can download at

Fixed in 1.0.4. Thanks for the help!
PHP Copyright © 2001-2021 The PHP Group
All rights reserved.
Last updated: Mon Jul 26 04:01:24 2021 UTC