09-19-2013 10:58 AM
so, since the Timeout issue is happening rather quickly, I guess I am dealing with an error somewhere inside the BrowserField or the ScriptEngine.
Thanks in advance.
09-20-2013 03:04 PM
There was an automatic timeout on scripts of 10 seconds - this was an (old) prevention to help ensure battery life didn't get sucked away, as well as to try and stabilize runaway web page scripts. That is the reason for that error.
When you say "rather quickly", is it sooner than 10 seconds?
09-20-2013 04:09 PM
Another possible reason
Are you using Ripple?
I've been using Ripple for interface design (yes, it actually has a use) but there seems to be some online activity (I wish I didn't have) going to some CDN called Heroku (actually - they look good - might try them myself)
Having said that - the Heroku - Ripple crashing Chrome is not to be recommended
I've noticed another affectation of Ripple as well but that one deserves a sep thread
Simply put, if not using Ripple then as Adam says it's summat in the JS
A point made recently may expain it, however- have you got a race?
This is the only other situation I could see such a thing happening
09-23-2013 05:46 AM
Thanks for your replies. I didn't check the exact time it takes yet, but 10 seconds could be about how long it takes, although I have the feeling that it happens sooner. I will have a look into it, is there a way to get around this issue?
I am only using JQuery (1.10.2 at the moment) and JQuery Mobile (but we will most likely drop that one as soon as possible). So, no ripple here.
09-23-2013 10:09 AM
09-24-2013 11:05 AM
Well, it looks like timeouts are a way to circumvent this "safeguard", I just put everything thats not vital at this point of initialization into a function I put into setTimeout(function, 1);
I consider this a workaround, not a fix. There most likely isn't a fix to this issue.