Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:88972
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.171 as permitted sender)
MIME-Version: 1.0
References: <CAO3MkaAfFXY0jgj7XWuhon13y6TuNizzZJ3R1WNPG7rUAc=3ag@mail.gmail.com>
In-Reply-To: <CAO3MkaAfFXY0jgj7XWuhon13y6TuNizzZJ3R1WNPG7rUAc=3ag@mail.gmail.com>
Date: Wed, 28 Oct 2015 18:08:36 +0000
Message-ID: <CAO3MkaC6xrdNYxJ_K248Rsmgw7jPaP=4JDepK33GfX_xfxrg-g@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7bd6bb5ae6741a05232e151a
Subject: Re: Debugings another Drupal PHP 7 failure
From: neclimdul@gmail.com (James Gilliland)

--047d7bd6bb5ae6741a05232e151a
Content-Type: text/plain; charset=UTF-8

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 <neclimdul@gmail.com>
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.
>
>

--047d7bd6bb5ae6741a05232e151a--