I think the problem is that Task pool constructor launches thread and
then tries to adjust priority without checking whether thread has
already terminated. Druntime can be partly blamed for absense of
functions which do things right, but task pool constructor is broken
anyway. Perhaps just comment out  if(priority != int.max) ...  for
some time untill core.thread is upgraded for proper priority support?

https://github.com/D-Programming-Language/phobos/blob/master/std/parallelism.d#L1393

2013/12/15 Brad Roberts <[email protected]>:
> I'm _this_ close to just removing the buggy thread priority code unless
> someone steps up to fix it.  I don't have the time to screw around with it
> and the failure rate due to that one issue is pathetic.
>
> Sigh,
> Brad
> _______________________________________________
> phobos mailing list
> [email protected]
> http://lists.puremagic.com/mailman/listinfo/phobos
_______________________________________________
phobos mailing list
[email protected]
http://lists.puremagic.com/mailman/listinfo/phobos

Reply via email to