php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #41972 PHP crashes in the middle of a dumping an object
Submitted: 2007-07-11 23:39 UTC Modified: 2007-07-20 01:00 UTC
Votes:1
Avg. Score:4.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:1 (100.0%)
Same OS:1 (100.0%)
From: e_p_17 at hotmail dot com Assigned:
Status: No Feedback Package: Scripting Engine problem
PHP Version: 5.2.3 OS: CentOS
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: e_p_17 at hotmail dot com
New email:
PHP Version: OS:

 

 [2007-07-11 23:39 UTC] e_p_17 at hotmail dot com 
Description:
------------
I apologize in advance for the poor quality of this bug report. I can't really give you any information on how to reproduce the problem because this happened on a production server and we had to fix it ASAP with no time to really troubleshoot.

We had been successfully running PHP 5.1.6, but decided to upgrade to 5.2.3. After upgrading, everything seemed to be working fine. However, we later discovered that payment transactions via Paypal's Website Payments Pro PHP SDK were not completing. 

Initially we thought it may have been Paypal or an incompatability between Paypal's WPP SDK and PHP 5.2, however, our minimal investigation found otherwise.

Using various script breaks and object dumps, we were able to succesfully reproduce a PHP crash every time we attempted to run a var_dump on an object created via one of the calls within the WPP SDK. The object was created successfully, but when we tried to var_dump it, PHP would crash in the middle of the var_dump operation.  

We know it's crashing because every time we tried to var_dump we would get this in our error log: "exit signal Segmentation fault (11)" and the output would simply terminate in a strange place like: "[_defaultObjectClassname] => stdClass ["

Note that no error messages are produced in the visible output - only the error log.

Simply reverting back to PHP 5.1.6 (same ./configure options etc.) fixes the problem.  

In my extremely limited wisdom, it almost seems like there's a memory/size limit on the object itself (the object was quite large).

Again, my apologies for not being able to submit a better bug report. It may not even be a bug, but I have never experienced anything like this before and since reverting to 5.1.6 fixed the issue completely, I can only assume it's something within the 5.2.3 build that's causing the problem.

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2007-07-11 23:47 UTC] johannes@php.net 
Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.php.net/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to "Open".

Thank you for your interest in PHP.
 [2007-07-20 01:00 UTC] php-bugs at lists dot php dot net 
No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Fri May 03 04:01:32 2024 UTC