sorry, no idea.
On Mon, Sep 26, 2016 at 9:01 AM PhistucK wrote:
> Yes, but I could not provide a reproduction case. :(
> At least not without approvals from managers, I guess.
>
> Do you happen to know when the next stable patch release is planned (that
> includes the
Yes, but I could not provide a reproduction case. :(
At least not without approvals from managers, I guess.
Do you happen to know when the next stable patch release is planned (that
includes the change)? I had to instruct the test teams to use
--js-flags="--no-crankshaft" for now, which is not
Thanks for tracking this down. In general, if you're willing / able to
provide a repro case, we're happy to investigate suchs bugs ourselves, so
you don't have to go through the trouble of bisecting this..
On Sun, Sep 25, 2016 at 6:06 PM PhistucK wrote:
> After bisecting,
After bisecting, the bug started at -
https://chromium.googlesource.com/v8/v8/+log/c93d868f..d83c3f0e
The bug stopped at -
https://chromium.googlesource.com/v8/v8/+log/f9a47d47..a255aa83
This leaves me with
https://chromium.googlesource.com/v8/v8/+/4dab7b5a1d6722002d47d0be2481cb65602a2451,
which