Bug #68453 [NoF->Opn]: FPM Process hangs in no-debug only

Edit report at https://bugs.php.net/bug.php?id=68453&edit=1 ID: 68453 Updated by: requinix@php.net Reported by: pegasus at vaultwiki dot org Summary: FPM Process hangs in no-debug only -Status: No Feedback +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 Previous Comments: ------------------------------------------------------------------------ [2014-12-30 15:25:40] pegasus at vaultwiki dot org I have provided feedback several times since opening this bug. The last time was only a few days ago. No one has responded to me with any suggestions with getting to the bottom of it for some time. There is a difference. Please make a real response before auto-closing it next time. ------------------------------------------------------------------------ [2014-12-30 10:42:52] php-bugs at lists dot php dot net No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Re-Opened". Thank you. ------------------------------------------------------------------------ [2014-12-25 16:59:50] pegasus at vaultwiki dot org Now over 1 month later I tried the newest update with no change. Since it seems like an infinite loop occurs, I reworked a recursive class so it no longer accesses itself recursively. This seems to have eliminated the infinite loop in PHP master, although the recursion worked without issue in PHP 5.6.x and lower. With this change, the script now actually shows an error message (whether it was the core issue originally or it is a new issue, I cannot be sure). However, the script still will not complete execution because of the following error: Fatal error: Cannot redeclare class [class_already_declared] in [file_that_doesnt_declare_that_class_at_all] on line 0 This new error makes absolutely no sense. It always happens when using require_once on a specific file and always claims the same class is trying to redeclare, but that file does not so much as mention the name of the class. And the "on line 0" is no help either. ------------------------------------------------------------------------ [2014-11-25 16:01:00] pegasus at vaultwiki dot org Recompiled today using the newest commit into a completely different --prefix, in case there was conflicting data in the old --prefix. This made absolutely no difference; PHP still hangs unless --enable-debug is used. ------------------------------------------------------------------------ [2014-11-20 17:20:34] pegasus at vaultwiki dot org 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. ------------------------------------------------------------------------ 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