Comment 3 for bug 1702785

I found a bug in the code as described in this issue: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1779583

The bug would not prevent the error you're seeing, however, there is a second fork() which, if it fails, will block that part of cron, which would therefore leak. So if it happens "on the wrong fork()", (1) you won't see any logs and (2) you get a cron "process" which gets stuck waiting for a second child that was never created.

I included a patch too.