Le 06/03/2014 06:45, David C. Rankin a écrit :
> On 03/03/2014 02:06 PM, François Andriot wrote:
>> [...]
> Francois,
>
>    I'll say it again, "you're good!"
>
>    Is the slave in #7 actually sending the "finished" and it never makes it to
> the job? Or is it not sending "finished" at all?
>
>    Is there any possibility that #7 does not occur because the slave does not
> know where to send "finished"? What links/connects the slave to the job? Is it a
> signal/slot, or some memory address that the job originally passed to the slave
> in #3? Or does the slave just generate the "finished" and pass some type of job
> number along with it after #6??
>
>    Could the slave/job connection created in #3 be broken somehow such that the
> reverse path in #7 no longer exits after the delay in #6?
>


Please check bug report #1902 : I've posted 2 patches there.
If it's confirmed working, I'll explain what I believe is the root cause 
of this problem.

Francois