On Thursday, 1 November 2018 at 11:17:00 UTC, Kagamin wrote:
> On Thursday, 1 November 2018 at 10:52:52 UTC, Kagamin wrote:
>> Looks like the whole task is corrupted, but its destructor is buggy anyway: tries to use GC-allocated pool. Does it crash deterministically?

Yes.

> Oh, no, the destructor is supposed to work for a task on stack, but since this task is corrupted, it runs in GC finalization.

Thanks. I'll try to bring it down to the smallest case. May take me a while.

On Friday, 2 November 2018 at 08:32:11 UTC, Pjotr Prins wrote:
> Thanks. I'll try to bring it down to the smallest case. May take me a while.

You can call GC.collect at the end of a test to see if it fails.

On Wednesday, 31 October 2018 at 11:33:14 UTC, kinke wrote:
> On Wednesday, 31 October 2018 at 11:29:56 UTC, Pjotr Prins wrote:
>> I suspect the D compiler itself because we also have a problem in DMD. Is there a bugzilla report on this already?
>
> I very much doubt that. It's much more likely that it's a druntime regression, if your code really isn't to blame.

It is fixed in ldc 1.14.0. Unit test pass again.