robert.nimax wrote: > > Hi, we had the same issue. This happens if there was a complex GUI having > many widgets because IE is...ah, you know about this. :-) > We solved this problem with partial disposing. So you´ve got to > reorganize your destruction logic and perform a clean-up stepwise. After > each step you have to give the control back to the browser like this: > [...] >
I have the same problem. IMHO, QooxDoo should divide the destruction process up into multiple events itself to avoid this problem. One strategy I use in our app (in many places) is to run a recurring event using setTimeout that does some work, then checks to see how much time it's used. If it has used more than 100ms, I setTimeout again to return in 100ms and immediately exit the event. This means we only run 100ms of computation in any given event, and -- assuming it takes more than 100ms to run 5M instructions -- we won't get the IE "script too slow" warning. (It's not always trivial to divide work up into little pieces like this, though, because you never want to leave data structures in an intermediate state.) According to Eric Lawrence at Microsoft, IE's 5M instruction limit is set in the registry, and the only way to reset the counter is to begin a new event. An incredibly annoying aspect of this warning is that there is no way to tell what was running when the dialog popped up -- even when you're running in the debugger. So the only thing you can do is run your code in the profiler, cause the popup (if it's easily repeatable), and see what used lots of cycles. Dave -- View this message in context: http://qooxdoo.678.n2.nabble.com/How-to-handle-script-timeouts-when-closing-windows-in-IE-tp5988939p5990231.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
