This is a race condition if the cpu is bogged down while running the test. I don't believe (all/any?) browsers require setTimeout (etc) callbacks to execute in order preferential to the time that they *should* have run if they could have. I could be wrong.