Bug #76233 [Com]: php-cgi.exe crash (see small dump)

Edit report at https://bugs.php.net/bug.php?id=76233&edit=1 ID: 76233 Comment by: 1978 dot jl at gmail dot com Reported by: 1978 dot jl at gmail dot com Summary: php-cgi.exe crash (see small dump) Status: Open Type: Bug Package: CGI/CLI related Operating System: All Windows PHP Version: 5.6.35 Block user comment: N Private report: N New Comment: Hi, after many tests, the crash doesn't appears when we deactivate the ioncube loader, but in this case, it reveals a "out of memory" PHP error. Then, it seems to be this "out of memory" PHP error that only crash the PHP process when the ioncube loader is loaded. The original error that cause this "out of memory" error seems to be in a miss use of laravel framework. Sorry to disturb you. Previous Comments: ------------------------------------------------------------------------ [2018-04-19 07:36:30] 1978 dot jl at gmail dot com Hi, I have open a ticket to ioncube support. Sorry for my error, I have also the crash on PHP 5.6.34. I will keep you informed about the response of the ioncube support. Greetings. ------------------------------------------------------------------------ [2018-04-18 17:44:41] cmb@php.net Thanks for further investigation! Since this *may* be an ionCube issue, I suggest to contact them. Anyhow, I have to bail out here, since I'm neither an engine guru, nor accustomed to ionCube. ------------------------------------------------------------------------ [2018-04-18 17:21:39] 1978 dot jl at gmail dot com Hi Christoph, after analyze with DebugDiag, the cause should be in a ioncube module (ioncube_loader_win_5.6.dll), the source code that cause this stack overflow seems to be : $property = null; // bad case $p = $my_object->$property; // seems to crash only when used in ioncube context, seems no crash if ioncube deactivated But I don't understand why this crash not appear on PHP 5.6.34 in same conditions. Greetings. ------------------------------------------------------------------------ [2018-04-18 13:18:19] cmb@php.net Okay, I was asking for a reproduce script, since the backtrace is not particularly helpful ("Stack unwind information not available. Following frames may be wrong."), and since the stack overflow might be caused by deep (infinite?) recursion in the userland code. Can you provide a debug backtrace[1]? Also note that PHP 5 will not receive normal bugfixes anymore, but only security fixes. So unless it can be shown that this issue is indeed a security issue, we won't fix it for PHP 5, so it might be best if you test the project under an actively supported PHP version[2] if possible. [1] <https://bugs.php.net/bugs-generating-backtrace-win32.php> [2] <http://www.php.net/supported-versions.php ------------------------------------------------------------------------ [2018-04-18 13:08:28] 1978 dot jl at gmail dot com Hi, Sorry, at this moment, we analyze the problem but the code is in a huge project, I couldn't extract a short script to reproduce this bug. Greetings. ------------------------------------------------------------------------ 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=76233 -- Edit this bug report at https://bugs.php.net/bug.php?id=76233&edit=1