# Debugings another Drupal PHP 7 failure - Thread: https://externals.io/message/88970 - Original archive: https://news-web.php.net/php.internals/88970 - Started by James Gilliland on 2015-10-28T17:13:27+00:00 - Messages: 2 - Reply by email to internals@lists.php.net - More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt --- ## #88970 — James Gilliland — 2015-10-28T17:13:27+00:00 URL: https://externals.io/message/88970#88970 So in an effort to fully support PHP 7 out of the box with the eminent release of Drupal 8, we're trying to track down some segmentation faults in our testing infrastructure. One that seems to be causing a lot of failures is listed here. https://bugs.php.net/bug.php?id=70805 Does anyone have any pointers on what might cause a problem with the code? Alternatively as commented on the issue, I'm happy to setup access for someone to valgrind the problem as well if someone wants to help us out. --- ## #88972 — James Gilliland — 2015-10-28T18:08:36+00:00 URL: https://externals.io/message/88970#88972 · In reply to: #88970 wrapping the service container code that is triggering this bug with `gc_disable()` and `gc_enable()` or calling `gc_collect_cycles()` before its run seems to "fix" the segfault which seems to suggests a garbage collection problem. On Wed, Oct 28, 2015 at 12:13 PM James Gilliland wrote: > So in an effort to fully support PHP 7 out of the box with the eminent > release of Drupal 8, we're trying to track down some segmentation faults in > our testing infrastructure. One that seems to be causing a lot of failures > is listed here. > > https://bugs.php.net/bug.php?id=70805 > > Does anyone have any pointers on what might cause a problem with the code? > Alternatively as commented on the issue, I'm happy to setup access for > someone to valgrind the problem as well if someone wants to help us out.