From: Gustaf N. <ne...@wu...> - 2015-06-01 08:28:53
|
Hi Joe, Am 31.05.15 um 21:54 schrieb Joe Mistachkin: > I was able to reproduce the issue locally; however, it appears to be > extremely timing sensitive. Adding some debugging printf's causes the > issue to disappear. timing is unfortunately a companion of concurrency related bugs. > When I was able to reproduce the issue, I saw most of the created threads > waiting on the "mutex locking" lock, which is acquired by AtForkPrepare. > The parent and child processes both end up releasing this lock (via > AtForkParent and AtForkChild, respectively). right. but this is a busy loop. After some more tests, i've got the suspicion that this is no loop lockup, but a bad timing behavior with probably non-linear behavior. One has to be just patient. The 100 (forking) threads are fully started for this example script after less then 2 minutes, then the script hangs (loops) for 3+ minutes, and then all threads are joined and the script exits after 6+ minutes .... AKIKT reliably! please vrfy. -g |