On 12/11/2017 07:18 PM, Joakim wrote:
> On Friday, 8 December 2017 at 09:33:03 UTC, Ali Çehreli wrote:

>> I failed to find a way for Druntime to be resilient when such threads
>> disappear. For example, the registered cleanup handler in thread.d is
>> called only for cancelled threads, not the ones that exit simply by
>> returning from their thread functions. (This is according to cleanup
>> handler spec.)
>
> I haven't had to try all these thread registration methods, perhaps
> because the apps I'm testing are much simpler or because I'm going the
> other way from D to Java most of the time.

If you haven't seen elsewhere on this discussion already, I think the problems were a number of issues in the druntime:

  https://github.com/dlang/druntime/pull/1989

Unfortunately, the test program I added fails for 32-bit target on Darwin_64_32. I'm trying to find a way to debug it.

Ali