Bug #69484 [Opn->Csd]: zend_mm_heap corrupted on some pages when opcache is enabled

Edit report at https://bugs.php.net/bug.php?id=69484&edit=1 ID: 69484 Updated by: berdir@php.net Reported by: berdir@php.net Summary: zend_mm_heap corrupted on some pages when opcache is enabled -Status: Open +Status: Closed Type: Bug Package: opcache Operating System: Linux PHP Version: master-Git-2015-04-19 (Git) -Assigned To: +Assigned To: berdir Block user comment: N Private report: N New Comment: I can no longer reproduce this, looks like @dmitry's fix solved this and most other segfaults that I had. There was only one segfault in the full test suite that I haven't been able to reproduce anymore, apparently when compiling something. See https://www.drupal.org/node/2454439#comment-9849683. Closing this. Previous Comments: ------------------------------------------------------------------------ [2015-04-20 10:32:56] berdir@php.net You can enable simpletest in the UI or with drush (get it from https://github.com/drush-ops/drush, make sure drush is in the path or call it directly), then call drush en simpletest. Did you actually install drupal first? Because otherwise you won't be able to enable it. But the --sqlite --dburl approach should work here as well. You do need to make sure that it's integrated into apache and available somewhere, in my case that's on http://d8, you need to update that. I'm pretty sure that the backtrace is correct, note that it's a backtrace from the separate apache process, that one segfaulted, not the test script. As mentioned, you can also reproduce this manually, by installing drupal, enabling aggregator module (same as simpletest) and then go to /aggregator/sources/add. ------------------------------------------------------------------------ [2015-04-20 09:53:25] laruence@php.net btw, are you sure you are get the right backtrace with right php binary? since #14 0x00007fd2738fbb65 in zend_execute_scripts (type=8, retval=0x7fd200001c07, retval@entry=0x0, file_count=3) at /home/berdir/tools/php-src/Zend/zend.c:1392 retval=0x7fd200001c07 should not be a valid pointer. ------------------------------------------------------------------------ [2015-04-20 09:34:57] laruence@php.net php7 core/scripts/run-tests.sh --dburl mysql://root:@127.0.0.1:3308/test --url http://d8/ --verbose --color --class "Drupal\aggregator\Tests\AddFeedTest" ERROR: Missing Simpletest database schema. Either install Simpletest module or use the --sqlite parameter. I don't understand how to install Simpletest ------------------------------------------------------------------------ [2015-04-20 06:31:48] berdir@php.net Oh, could he curl problem be the segfault that I've seen in https://bugs.php.net/bug.php?id=69411 that was related to curl? We've committed a workaround four that (no longer doing that http request) but I will check if that fixed the problem there. The fatal error stuff often happens when page requests fail, our tests unfortunately don't abort on the first fail but try to continue, so if a form submission fails, then an object is loaded that was expected to be created and then a method call on that fatals. Did you check your apache log? Or going to the mentioned page manually? You can also try --color --verbose on the test runner, that should display the detailed output and the effect that I've seen there was some 0 bytes responses. ------------------------------------------------------------------------ [2015-04-20 04:03:06] laruence@php.net While I am running : php7 core/scripts/run-tests.sh --dburl sqlite://tmp/sqllite --sqlite --url http://d8/ --verbose --color --class "Drupal\aggregator\Tests\AddFeedTest" I found a segfault in resource handling(via curl), and is fixed in : https://github.com/php/php-src/commit/d66045fe73fb646f15a45286313231908e656a37 after that I see a FATAL ERROR: Fatal error: Call to a member function refreshItems() on null in /home/huixinchen/opensource/github/drupal/core/modules/aggregator/src/Tests/AddFeedTest.php on line 21 FATAL Drupal\aggregator\Tests\AddFeedTest: test runner returned a non-zero error code (255). is that expected? ------------------------------------------------------------------------ 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=69484 -- Edit this bug report at https://bugs.php.net/bug.php?id=69484&edit=1