GC deadlocks on linux
Byron Heads via Digitalmars-d-learn
digitalmars-d-learn at puremagic.com
Wed Feb 18 13:26:34 PST 2015
On Wednesday, 18 February 2015 at 21:21:11 UTC, Byron Heads wrote:
> On Wednesday, 18 February 2015 at 21:05:10 UTC, Byron Heads
> wrote:
>> On Wednesday, 18 February 2015 at 20:55:56 UTC, ketmar wrote:
>>> On Wed, 18 Feb 2015 20:35:44 +0000, Byron Heads wrote:
>>>
>>>> On Wednesday, 18 February 2015 at 20:33:40 UTC, ketmar wrote:
>>>>> On Wed, 18 Feb 2015 20:27:07 +0000, Byron Heads wrote:
>>>>>
>>>>> are you forking? ;-)
>>>>
>>>>
>>>> I am in the daemonize library
>>>>
>>>> https://github.com/NCrashed/daemonize
>>>
>>> can you drop that and just let the program run on foreground?
>>> i suspect
>>> that it may solve your problem. you can detach your program
>>> with "setsid"
>>> and "&" to avoid forking.
>>>
>>> `fork()` is a very fragile thing, and it may be the source of
>>> heisenbugs.
>>> stop `fork()`ing may be the easiest solution (if it solves
>>> something, of
>>> course ;-).
>>
>> By passing daemonize with the GC enabled is working.. going to
>> dig into the signals and see if thats it.
>
>
>
> My guess is this is going to be related to forking, going to
> see if I can make a test case.
Might be related:
https://issues.dlang.org/show_bug.cgi?id=6846
More information about the Digitalmars-d-learn
mailing list