From: ohornoiu at bellevuechristian dot org Operating system: Mac OS X 10.2.6+ PHP version: 4.3.3 PHP Bug Type: Reproducible crash Bug description: Long Scripts Consistently Segfault
Description: ------------ This bug is a reference to Bug #25394 which was deemed "bogus" without any serious research by the developers. This is a very serious bug which basically results in the inability to create rich, meaningful applications on OS X since php consistently and mindlessly crashes on this platform. The venom with which this topic was approached by the developers in this forum in the past is entirely innapropriate for an open source project and I expect a more fair and thorough investigation this time since I am providing a concrete script that is part of a huge 77,000 line project for school calendaring called Kronophobia. I am the lead developer of this project and some of my users have requested to run this project on Mac OS X only to find out that this bug affects them in such a way as to make using the program impossible. This bug does not exist in Linux, FreeBSD or OpenBSD, all of which have been thoroughly tested and we support. If the php developers refuse to look at this code for some reason because it is "beneath" them to fix a Mac problem since they do not care about Mac OS X then I would at least expect some sort of public statement about this and an explanation to the Mac community of why they are to be ostracized. Reproduce code: --------------- The Kronophobia package is available from the following url: http://kronophobia.sourceforge.net The main file of the project, index.php is the affected file as it spans roughly 7,000 lines of code. Expected result: ---------------- When run on any other platform besides Mac OS X, the code renders the page in question flawlessly. The page is just a series of switch() statements with multiple includes for each case. Actual result: -------------- The actual result is an apache segfault, a "Page not Found" error results in the browser and a crash is logged in apache logfiles. NO, increasing the memory limit in PHP does NOT fix this problem like some have suggested and PHP seems to only use about 1 megabyte of memory even after 7k lines of code. -- Edit bug report at http://bugs.php.net/?id=25738&edit=1 -- Try a CVS snapshot (php4): http://bugs.php.net/fix.php?id=25738&r=trysnapshot4 Try a CVS snapshot (php5): http://bugs.php.net/fix.php?id=25738&r=trysnapshot5 Fixed in CVS: http://bugs.php.net/fix.php?id=25738&r=fixedcvs Fixed in release: http://bugs.php.net/fix.php?id=25738&r=alreadyfixed Need backtrace: http://bugs.php.net/fix.php?id=25738&r=needtrace Try newer version: http://bugs.php.net/fix.php?id=25738&r=oldversion Not developer issue: http://bugs.php.net/fix.php?id=25738&r=support Expected behavior: http://bugs.php.net/fix.php?id=25738&r=notwrong Not enough info: http://bugs.php.net/fix.php?id=25738&r=notenoughinfo Submitted twice: http://bugs.php.net/fix.php?id=25738&r=submittedtwice register_globals: http://bugs.php.net/fix.php?id=25738&r=globals PHP 3 support discontinued: http://bugs.php.net/fix.php?id=25738&r=php3 Daylight Savings: http://bugs.php.net/fix.php?id=25738&r=dst IIS Stability: http://bugs.php.net/fix.php?id=25738&r=isapi Install GNU Sed: http://bugs.php.net/fix.php?id=25738&r=gnused Floating point limitations: http://bugs.php.net/fix.php?id=25738&r=float
