Bug #68453 [Com]: FPM Process hangs in no-debug only

From: Date: Wed, 19 Nov 2014 18:33:02 +0000
Subject: Bug #68453 [Com]: FPM Process hangs in no-debug only
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-188689@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=68453&edit=1 ID: 68453 Comment by: pegasus at vaultwiki dot org Reported by: pegasus at vaultwiki dot org Summary: FPM Process hangs in no-debug only Status: Open Type: Bug Package: Reproducible crash Operating System: Centos 6 64-bit PHP Version: master-Git-2014-11-19 (Git) Block user comment: N Private report: N New Comment: Well I tried for a few hours but cannot create a simple test that duplicates the results. Although my results varied and the same code blocks did not consistently hang from test to test, the total script would always hang. Before giving up when it seemed the behavior changed, I thought this was related to: Caching object instances as array entries of static arrays declared inside a getObject method, inside other objects that were cached in the same way in higher level objects (depth of 3 or higher), then starting from the highest-level object, trying to retrieve the deep objects. But I cannot be sure because the simple test succeeds, and it seemed like the original script would hang on the return statements, which makes it nearly impossible to debug further from within PHP. As I said, this worked properly in previous commits, but the last commit I tried before today is dated 11/6/2014, so I am not sure when the breaking change occurred. I will try to at least narrow it down to the last date with a working commit and report back. Previous Comments: ------------------------------------------------------------------------ [2014-11-19 17:06:41] pegasus at vaultwiki dot org Description: ------------ On certain PHP scripts, the process hangs indefinitely. This is new behavior that I did not experience several days ago on an earlier build. I have not yet been able to determine what code block is related, but I am working on that now. As far as I can tell, there is no SIGSEV or other logged crash; the process just eventually times out. This behavior exists in both no-debug-non-zts and no-debug-zts builds. It does not occur in debug-non-zts (I have not tested debug-zts). Therefore, it suggests that one of the debug symbols that is removed in no-debug builds is actually needed for execution somewhere or that the removal of debug symbols might damage non-debug code in some way. The behavior persists if opcache is disabled. Here is the configure line, if it helps: ./configure --enable-bcmath --enable-libxml --enable-mbstring --enable-sockets --enable-fpm --enable-opcache --prefix=/home/php --with-curl --with-freetype-dir=/usr --with-gd --enable-gd-native-ttf --with-jpeg-dir=/usr --with-libdir=/lib64 --with-libxml-dir=/usr/lib64/ --with-mcrypt --with-mysql --with-mysqli --with-openssl=/usr --with-pic --with-png-dir=/usr --with-xpm-dir=/usr --with-xsl --with-zlib --with-zlib-dir=/usr --with-fpm-user --with-fpm-group Expected result: ---------------- Normal execution ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=68453&edit=1

« previous php.bugs (#188689) next »