[Issue 15939] GC.collect causes deadlock in multi-threaded environment

via Digitalmars-d-bugs digitalmars-d-bugs at puremagic.com
Thu May 12 09:50:49 PDT 2016


--- Comment #14 from safety0ff.bugz <safety0ff.bugz at gmail.com> ---
(In reply to Aleksei Preobrazhenskii from comment #13)
> All suspending signals were delivered, but it seems that number of calls to
> sem_wait was different than number of calls to sem_post (or something
> similar). I have no reasonable explanation for that.
> It doesn't invalidate the hypothesis that RT signals helped with original
> deadlock though.

I haven't looked too closely at whether there's any races for thread
My suspicions are still on a low-level synchronization bug.
Have you tried a more recent (3.19+ kernel) or trying to newer glibc?

I'm aware of this bug [1] which was supposed to affect kernels 3.14 - 3.18 but
perhaps there's a preexisting bug which affects your machine?

[1] https://groups.google.com/forum/#!topic/mechanical-sympathy/QbmpZxp6C64


More information about the Digitalmars-d-bugs mailing list