ID: 34978
User updated by: cdc at ccicon dot com
Reported By: cdc at ccicon dot com
Status: Open
Bug Type: Reproducible crash
Operating System: linux i386
PHP Version: 5.0.5
New Comment:
The zend.ze_compatiblity_mode is set to 1 in the index.php file and
several other files using the following test for php version number
if (substr(phpversion(), 0, 1) == "5") {
ini_set("zend.ze1_compatibility_mode", "1");
}
Disabling this option (ie zend.ze_compatiblity_mode=0) under php 5.0.5
and under the last cvs snapshot that was recommended seems to solve
this race condition. I have not tested the code fully to see that this
hasn't introduced other problems. However, it does remove the out of
memory and segfault problems.
Were there changes made in php 5.0.5 and later that make this option
obsolete. Or, will disabling this condition lead to other compatility
issues?
TTYL
CDC
Previous Comments:
------------------------------------------------------------------------
[2005-10-27 18:53:57] cdc at ccicon dot com
I assume you meant ze1_compatiblity_mode and compact was just a typo?
Yes compatibility_mode is set. It is explicitly set numerous places
within the Sugar Code. I can try changing it, but I'm assuming it was
set within the code for a reason.
I'll try changing it and see what happens.
------------------------------------------------------------------------
[2005-10-27 17:27:49] [EMAIL PROTECTED]
When getting the error is ze1 compact mode enabled or disabled and does
changing the setting alter the behaviour in any way?
------------------------------------------------------------------------
[2005-10-27 11:56:02] [EMAIL PROTECTED]
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] [EMAIL PROTECTED]
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?
------------------------------------------------------------------------
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
