#34978 [Opn]: php out of memory or segmentation fault while installing sugarcrm 3.5.1a
| From: | iliaa@php.net | Date: | Thu, 27 Oct 2005 15:27:50 +0000 |
| Subject: | #34978 [Opn]: php out of memory or segmentation fault while installing sugarcrm 3.5.1a | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-87144@lists.php.net to get a copy of this message | ||
ID: 34978
Updated by: iliaa@php.net
Reported By: cdc at ccicon dot com
Status: Open
Bug Type: Reproducible crash
Operating System: linux i386
PHP Version: 5.0.5
New Comment:
When getting the error is ze1 compact mode enabled or disabled and does
changing the setting alter the behaviour in any way?
Previous Comments:
------------------------------------------------------------------------
[2005-10-27 11:56:02] rrichards@php.net
I can't say the exact point of failure (though its due to how the
objects are linked to each other), but I recently had to get a highly
modified version of this running under 5.1 and it was falling into
infinite loops. Had to disable the ze1.compatibility_mode, remove the
majority of explicit reference usage (xxx = & object) and use some
explcit clone calls in spots. Runs stable after those changes, so not
sure if this is just a PHP compatbility issue.
------------------------------------------------------------------------
[2005-10-26 21:00:22] cdc at ccicon dot com
From the application logs, it is apparent that many hundreds, even
thousands of lines of code are executing successfully after the post
before this out of memory condition occurs. I have not yet been able
to trace the exact code location as I cannot step the code in my Zend
Studios environment using php 5.1. It appears the the code may be
dying on either and array_merge or in a mysql call. I will roll back
to php 5.0.5, which I can step in the Zend debugger, and attempt to
isolate the exact section of code which is generating these errors. If
I can locate it, I can perhaps write a small test script to reproduce
the error under the CVS snapshot release.
This will likely take me a day or two to complete.
Thanks for your continued attention to this problem.
TTYL
CDC
------------------------------------------------------------------------
[2005-10-26 17:10:04] iliaa@php.net
Can you create some sort of a simple test case?
For example if you pass all get/post/cookie data from the failing
request to <?php phpinfo(); ?> script do you get the same error?
------------------------------------------------------------------------
[2005-10-26 16:43:04] cdc at ccicon dot com
I realize that a general out of memory condition is not a bug.
However, this appears to be some kind of race condition that is
consumming memory. This problem in new since version 5.0.4. The same
code runs fine under 5.0.4 but generates this race condition in 5.0.5
and newer.
As you can see from the error message below, I already have the
memlimit set at 64M. I started at 16. It makes no difference where I
have it set, the race condition consumes all available memory and fails
with an out of memory error.
I will attempt to isolate the code in sugar which is resulting in the
race condition, however, the fact remains that this code runs fine
under 5.0.4 and does not run under new versions.
------------------------------------------------------------------------
[2005-10-26 16:35:53] iliaa@php.net
Sorry, but your problem does not imply a bug in PHP itself. For a
list of more appropriate places to ask for help using PHP, please
visit http://www.php.net/support.php as this bug system
is not the
appropriate forum for asking support questions. Due to the volume
of reports we can not explain in detail here why your report is not
a bug. The support channels will be able to provide an explanation
for you.
Thank you for your interest in PHP.
Out of memory is not a bug in PHP, it simply means the memory limit
needs to be increased. Try setting it to 20 megs and see if that solves
the problem.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/34978
--
Edit this bug report at http://bugs.php.net/?id=34978&edit=1