Hi Jens, thank you for your reply. I did not know Opera started using V8, things make more sense now! Anyway, as an act of desperation we have started compiling older revisions of the code and testing them to see if they show the same behaviour. And we found one which works normal! So now we are going revision by revision and doing witch hunting, to try and isolate the malicious piece of code.
Once we have that figured out, I will file an issue on the right tracker, given it is not a human error. Will post an update once we track it down. On Tuesday, August 13, 2013 8:40:13 PM UTC+12, Jens wrote: > > First I would check if its really no JavaScript/GWT code that goes wild > after a while. I think I would just start CPU profiling using Dev Tools and > keep an eye on it until CPU usage increases. > > Other than that you probably have more luck solving it by asking the > Chrome guys. Btw its not surprising that it also happens in Opera because > since Opera 15 the browser is based on Chrome's Blink + V8 engines. Try > older versions of Chrome also. Maybe there is a version that does not have > this problem. > > -- J. > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
