For what it's worth: I have ran in the same issue when I recently started to work on a medium "sized" laptop.
I have never had (and have) this issue with the same and other projects running on a good desktop. Hence it seems not to be project but more machine dependent. I suspect memory, but don't know how to verify this. R On Thursday, 28 March 2013 17:57:29 UTC+1, Michael Prentice wrote: > > No luck. Just ran into this again. Restarting Chrome, again, fixed it. > > On Wednesday, March 27, 2013 2:28:50 PM UTC-4, Michael Prentice wrote: >> >> OK, I'll give that a shot with: >> >> *-XX:MaxPermSize=384m* >> >> Thanks a lot. >> >> On Wednesday, March 27, 2013 10:03:08 AM UTC-4, xsee wrote: >>> >>> Try setting your maxPermSize in the VM args section of your launch >>> config (mine is at 384). This keeps my Chrome plugin running all day with >>> no problems on a medium sized project. >> >> -- 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.
