megatronx - yeah, I tried stuffing about with the timing since then, wait X, wait for signal, etc. and haven't managed to change things.
@Colludium - Yep, happens in all browsers, on html5 export and node webkit preview. Also just tried your advice and cleared cache to no avail. I have it setup so when the marker has a boolean of 'notSet' to true, it will create all that stuff and the set the boolean to false. So, it should definitely be triggering (and it is on debug).
Well thanks guys, but I'm really at a loss now and will just have to try re-writing it in a different way I guess. Let's hope the new version will go a bit smoother.