Bug #77194 [Fbk->NoF]: php7ts.dll crashing when running embed

Edit report at https://bugs.php.net/bug.php?id=77194&edit=1 ID: 77194 Updated by: php-bugs@lists.php.net Reported by: svbussww at 126 dot com Summary: php7ts.dll crashing when running embed -Status: Feedback +Status: No Feedback Type: Bug Package: Reproducible crash Operating System: Windows 7 PHP Version: 7.2.12 Assigned To: cmb Private report: N New Comment: 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. Previous Comments: ------------------------------------------------------------------------ [2022-11-17 13:24:30] cmb@php.net This might have the same root cause than GH-9650[1], and as such would be fixed now. Can you please check that out? [1] <https://github.com/php/php-src/issues/9650> ------------------------------------------------------------------------ [2019-10-12 22:38:12] jake at qzdesign dot co dot uk Seems with XDebug enabled, I at least get "Script phpunit ... handling the ... event returned with error code -1073741819" from Composer. But still can't find anything in Event Viewer since latest Windows update. This isn't AFAIAA running multithreaded, though is with the MT dist. We're not actively using ext-pthreads (and not at all unless enabled in the default php.ini). I've tried doubling memory_limit and it makes no difference. My issue might not be the same but does at this stage appear related (though the OP states "running embed"). It's the closest-matching existing issue I could find, and it's a similar-looking crash in php7ts.dll. Like I said, heap corruption coming from somewhere?? ------------------------------------------------------------------------ [2019-10-12 00:19:01] jake at qzdesign dot co dot uk Some comments suggest multithreading issue. Any way to run Composer/PHP restricted to one thread (with multithreaded install)? Could try that and see if problem goes away. Won't be conclusive but might provide clue. ------------------------------------------------------------------------ [2019-10-11 23:59:53] jake at qzdesign dot co dot uk I think there is a heap corruption issue in PHP, at least in the Windows (x64) build. I've got some complex tests (running via PHPUnit), and I hit this issue almost every time. Sometimes the tests will run to completion, but most times they'll crash at some different point. It will be an APPCRASH at one of about three or four apparently random points in the process. And always at the same address in php7ts.dll. As I'm sure you can understand, it's difficult to isolate this further. I can confirm it happens with both PHP 7.1.30 and 7.3.4. This is further frustrated by a Windows 10 update (yes, I know, we need to stop these forced updates from Microsoft, but easier said than done) to version 1903 (18362.418) which appears to silence APPCRASH: it no longer appears in the Event Log, and Composer is unable to detect the 'return value' exception code but is forced to exit silently itself. Any suggestions on how to restore logging of APPCRASH events since this latest Microsoft atrocity would be welcomed... ------------------------------------------------------------------------ [2019-02-14 18:13:00] ab@php.net I don't think the patch is the right solution to this after all. The issue seems to be very specific and affect some specific system configuration. In fact, i couldn't confirm there are issues with the memory manager. The change as in the patch would introduce memory fragmentation in opposite to VirtualAlloc, which would affect performance. 32-bit might be well more affected, but from the backtraces the build used seems to be actually 64-bit. Given Windows 7 reaches EOL in less than a year and such issues are not massively reported, probably the issue is a low priority. Thanks. ------------------------------------------------------------------------ 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=77194 -- Edit this bug report at https://bugs.php.net/bug.php?id=77194&edit=1