In reply to dave_59:
This sounds like a silly question but I am still not able to understand if #1 delay before fork-join_none can be treated as a blocking statement to start the execution of spawned processes, then why does display statement after fork-join_none is executed(printed) before the display statement in fork-join_none.
(Why does the spawned process wait until the parent thread terminates?)
As per my understanding, fork-join_none should start execution as soon as the parent thread executes a blocking statement (#1 before fork-join_none).