Behavior.initialize() is called from user thread, as a result of setLive,
instead of from BehaviorScheduler thread. This leads to a race condition where a
Behavior could miss having its initial wakeup condition triggered if the wakeup
condition is satisfied right away. The following test program demonstrates this
with a call to Behavior.postId that is done immediately following the Behavior
being added to the scene graph. The Behavior calls wakeupOn(), to wakeup on
behavior post, from its initialize() method. Occasionally, the post is missed.
To reproduce this, run the attached program, create the scene graph, and then
start the test. If you check the "Rotate" option before creating the cube
(causing it to spin), it will fail more quickly.