#34978 [Opn->Fbk]: php out of memory or segmentation fault while installing sugarcrm 3.5.1a

ID: 34978 Updated by: tony2001@php.net Reported By: cdc at ccicon dot com -Status: Open +Status: Feedback Bug Type: Reproducible crash Operating System: linux i386 PHP Version: 5.0.5 New Comment: Thank you for this bug report. To properly diagnose the problem, we need a backtrace to see what is happening behind the scenes. To find out how to generate a backtrace, please read http://bugs.php.net/bugs-generating-backtrace.php Once you have generated a backtrace, please submit it to this bug report and change the status back to "Open". Thank you for helping us make PHP better. Previous Comments: ------------------------------------------------------------------------ [2005-10-25 22:25:08] cdc at ccicon dot com When using the suggested snapshot, the installer manages to complete successfully. However, first login generates the following error when register_long_arrays is set ON ( Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 47 bytes) in /home/www/dev/htdocs/sugarsuite-3.5.1a/data/SugarBean.php on line 1087 When register_long_arrays is set off, php generates a segfault, which is apparently a documented problem with Sugar and php5. This segfault condition also exists in php 5.0.4, however, turning register_log_arrays=On solves this problem in 5.0.4. ------------------------------------------------------------------------ [2005-10-25 19:14:26] tony2001@php.net Please try using this CVS snapshot: http://snaps.php.net/php5-latest.tar.gz For Windows: http://snaps.php.net/win32/php5-win32-latest.zip ------------------------------------------------------------------------ [2005-10-25 19:08:58] cdc at ccicon dot com Description: ------------ When installing sugarcrm vs 3.5.1a (or earlier) php 5.0.5 generates a out of memory error, or, if >36Meg memory, will generate a segfault. This problem is reproducible with both apache 2.0.54, 2.0.55, sugarcrm 3.5.1, 3.5.0, 3.0. I also tested the php 5.0.6-dev snapshot from 200510251443 and it exhibited the same problem. Php 5.0.4 does not exhibit this problem. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=34978&edit=1