The 'm' associative array gets cloned on thread creation.
Ok, i see now. My understanding is that there is one global instance of the component node, even if it has spawned a number of threads.
In that case m.top for all threads point to the same instance and are subject to rendezvous when accessing fields in m.top.
<component name = "TestScene" extends = "Scene" >
<script type = "text/brightscript" >
task1 = m.top.findNode("Task1")
task1.control = "RUN"
task2 = m.top.findNode("Task2")
task2.control = "RUN"
m.top isn't the Scene, it's the task component itself. So fields on the task node are m.top.<field> and the unique id of the task component is m.top.id.