#21478 [Ver]: Zend/zend_alloc.c :: shutdown_memory_manager produces segfault

ID: 21478 Updated by: black@php.net Reported By: pollita@php.net Status: Verified Bug Type: Scripting Engine problem Operating System: linux PHP Version: 4CVS-2003-01-06 (dev) New Comment: this bug just doesnt seem to get away fully... i've acctually (on the safe side) got around to compile 4.3.1 stable official release and using it on the software.. i still get occasional random segfaults.. but the problem is that they occur after some time, and i cant reproduce them in any way, because they are TOTALLY random.. is a funny memory leak of somekind possible? im getting more bugs than ever, and i can't seem to put a finger on either one of them, it appears every time i start gdb on apache i cant bring it to crash... i tried this now for atleast an hour, with no success.. ugh it hit me... thread safety perhaps? i've tried in gdb and as far as i understand that is only 1 thread.. and i couldnt reproduce it inside gdb... i have http://sunshine.krneki.org/phpinfo.php ... to go over it the extensions i really use are ftp, gd2, sockets, mysql, xml, aggregate (i think this isnt an extension, but i noticed "object overloading" in phpinfo somewhere).. im unsure about the rest.. is it possible that one of theese extensions isnt quite thread safe? i also use stuff like "function &mod($name)" inside an object to return a reference to an object.. and then $var = &$obj->mod("name"); to assign it in the code.. since this is the.. one.. probablly only major change i did to the code besides using aggregate() and ... well.. nothing else... dual proc or not, the segfaults still happen... my next "sollution/test" will be to remove references from the code and try to solve modularity in a more "global" type of way... to see if the crashes go away... i have about a week to come up with something, then it's serious ass raping time, cause ill miss a BIG BIG BIG deadline. if someone wants to look at the code, i have no problem in putting up a tgz with a test database.. but realise that a small reproducible script is wishfull thinking.. just the /include dir should be around 170k (but it is clean code, really ;)) any guides how i could debug this in threaded mode / all apache threads? Previous Comments: ------------------------------------------------------------------------ [2003-03-25 10:55:16] black@php.net I'm setting back to verified, since polita infact has a reproducable version above? As i said, i might be wrong and mine is not related to politas directly, but the same behaviour applies (only a bit different backtrace which leads me to the conclusion that the behaviour might not be related). ------------------------------------------------------------------------ [2003-03-20 17:06:04] sniper@php.net Closed then. ------------------------------------------------------------------------ [2003-03-20 03:06:54] black@php.net sniper: i tried the latest stable snapshot (php4-STABLE-200303200830) and i couldnt reproduce the bug anymore.. but then, if its as elusive as polita said in #2 any changes to the code might have made it dissapear (had lots of them in the last 2 days).. I also tried php4-200303182230 to confirm that that might not be the case, but it has gone away also... if i spot any more segfaults ill do the wise thing and archive the scripts / database, if it can be reproduced ;) ------------------------------------------------------------------------ [2003-03-19 15:53:36] sniper@php.net I don't know what this 4.5-dev is..since the only official development branches are PHP_4_3 and the php5 module. Try this snapshot: http://snaps.php.net/php4-STABLE-200303192030.tar.gz If that doesn't work, but the RC1 works, then it's a problem with the build tools on the snaps.php.net machine. (Please send me that test script you used when testing 4.3.2-RC1) ------------------------------------------------------------------------ [2003-03-19 15:18:36] black@php.net sniper, yes, i wasn't able to reproduce it on php4.3.2rc1 i did have one segfault it normal operation mode (not inside gdb), but i couldnt reproduce it in any way or form similar to the process of reproducing on the latest -STABLE or 4.5-dev snapshots as far as i can tell 4.3-dev and 4.5-dev are subject to this.. im not even going to guess what goes on in 5.0-dev yet.. btw, there is a slight difference between the backtrace ilia got above and mine, so it might be an unrelated problem... still the same scope and behaviour thou. ------------------------------------------------------------------------ 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/21478 -- Edit this bug report at http://bugs.php.net/?id=21478&edit=1