I have also stumbled upon another similar issue (i.e. broken in Safari on iOS6 but working in Chrome on the same system) where number comparison breaks down after about 6000 iterations following a specific pattern: http://code.google.com/p/google-web-toolkit/issues/detail?id=7844
As I observed in the already mentioned http://dev.vaadin.com/ticket/10753, adding something like if (false) return new Object(); or "".split(); made that problem go away. I have not tested these "workarounds" together with the 2000 < 0 or a++ problems, but it could be worth a try for a generic hack that should have a quite insignificant impact on performance. It seems that just rewriting a++ would not be enough considering the other types of problems identified (2000 < 0 and random ClassCastException). -- -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups "Google Web Toolkit Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
