WaitOnExit causes the main thread to wait until the backend finishes.
This means it will hang the main thread making the GUI irritatingly
unresponsive. Thus, the only way out is to use multi-threading.
Regarding zombies, these were automatically adopted by the frontend as
terminating the latter also reaped all of them.
Edward
On 30/08/2015, tilt! <tilt@???> wrote:
> Why does WaitOnExit() imply multithreading? All it does is wait for the
> process to exit.
>
> Best regards,
> T.
>
> Am 30. August 2015 16:57:54 MESZ, schrieb Edward Bartolo
> <edbarx@???>:
>>I explicitly avoided to use WaitOnExit() to avoid having to use
>>multi-threading which I wanted to avoid. I will try to create a
>>descendant of TThread to use it to Connect and Disconnect but I need
>>to be cautious to avoid complicating the code.
>>
>>On 30/08/2015, Edward Bartolo <edbarx@???> wrote:
>>> Merge accepted.
>>>
>>> Kind regards,
>>> Edward.
>>>
>>> On 30/08/2015, tilt! <tilt@???> wrote:
>>>>
>>>>
>>>> On 08/30/2015 07:40 AM, Edward Bartolo wrote:
>>>>> OK, poWaitOnExit added and zombies creation has been reduced.
>>However,
>>>>> I am still getting these:
>>>>>
>>>>> 3584 ? 00:00:00 kworker/u8:0
>>>>> 3586 ? 00:00:00 kworker/1:3
>>>>> 3588 ? 00:00:01 netman
>>>>> 3623 ? 00:00:00 ifdown <defunct>
>>>>> 3644 ? 00:00:00 kworker/0:0
>>>>> 3645 ? 00:00:00 kworker/0:3
>>>>> 3898 ? 00:00:00 ifup <defunct>
>>>>> 4142 ? 00:00:00 ifdown <defunct>
>>>>> 4163 ? 00:00:00 kworker/0:4
>>>>> 4186 pts/0 00:00:00 ps
>>>>>
>>>>
>>>> Please accept merge request #4 which should fix the issue for the
>>>> backend executable.
>>>>
>>>> Kind regards,
>>>> T.
>>>>
>>>
>
> --
> Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
::
Re: [DNG] BUG: zombies increase whi…
