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

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: Feedback 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: I always remove the build directory completely before attempting a new update. Even so, I did what you suggested and there was no change in this behavior. I then went and manually removed the conflicting libs it was complaining about, and on the next compile there were no complaints. There was still no change in this behavior. I have a feeling that there is somewhere else in PHP internals that is not expecting the new Bucket definition, that still might be somehow coded for the old one. Or perhaps there is a location that is not using the Bucket at all when it should be. To check my suspicions from my first post, I then went and compiled PHP as debug-zts. As I suspected, this works properly. So it is only no-debug builds that are affected by this bug. Previous Comments: ------------------------------------------------------------------------ [2014-11-20 07:33:56] rasmus@php.net You did a full "make distclean && ./buildconf -f" ? ------------------------------------------------------------------------ [2014-11-20 07:09:31] pegasus at vaultwiki dot org Yes, I just recompiled again and the timestamp is updated on opcache.so. But like I said removing that extension from php.ini to disable it has no effect, so it's not hanging because of any extension I've defined there. However, I am seeing these warnings when compiling now. Not sure what to do about them: /usr/bin/ld: warning: libssl.so.10, needed by /usr/lib64/libssh2.so.1, may conflict with libssl.so.1.0.0 /usr/bin/ld: warning: libssl.so.10, needed by /usr/lib64/libssh2.so.1, may conflict with libssl.so.1.0.0 /usr/bin/ld: warning: libcrypto.so.10, needed by /usr/lib64/libssh2.so.1, may conflict with libcrypto.so.1.0.0 /usr/bin/ld: warning: libcrypto.so.10, needed by /usr/lib64/libssh2.so.1, may conflict with libcrypto.so.1.0.0 /usr/bin/ld: warning: libcrypto.so.10, needed by /usr/lib64/libssh2.so.1, may conflict with libcrypto.so.1.0.0 /usr/bin/ld: warning: libcrypto.so.10, needed by /usr/lib64/libssh2.so.1, may conflict with libcrypto.so.1.0.0 ------------------------------------------------------------------------ [2014-11-20 06:37:05] rasmus@php.net Well, just check the timestamp ------------------------------------------------------------------------ [2014-11-20 06:33:58] pegasus at vaultwiki dot org The only extension in my php.ini is zend_extension = "opcache.so" I was under the impression that this recompiles in tandem with every PHP recompile, as I've never actually compiled that module manually. ------------------------------------------------------------------------ [2014-11-20 05:58:05] rasmus@php.net I suppose this could matter if you have shared extensions that you didn't recompile after that change since the order changed in that Bucket struct. Check that all your .so extensions were compiled against this new struct layout. ------------------------------------------------------------------------ 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 https://bugs.php.net/bug.php?id=68453 -- Edit this bug report at https://bugs.php.net/bug.php?id=68453&edit=1