Ok - I just think I figured it out: I had 6 break points set in eclipse - these break points would not be hit at all during launch - but once I removed them all (right click - remove all) then FF + Chrome launches at 'normal' development speed.
Thanks!!! On Friday, October 19, 2012 9:43:55 AM UTC-7, Jorn Nordahl wrote: > > I get this from time to time... it is sooooo slow all of a sudden and it > usually happens when I am debugging away using FireFox as the browser... > (we only use FF as the browser to debug). When restarting after a code > change - there it is - slow as heck.... FF eventually allows me into the > app - but Chrome tells me to kill the page over and over since it times > out. > > I try to build, rebuild, rebuild again.... restart the box, clear out > cache, run mvn clean untill I'm blue in the face..... don't know what is > going on... Then - all of a sudden - it's ok again... > > If I connect directly to the tomcat server (production mode) then > everything is smooth and quick as it normally is - if I then switch over to > starting the app in eclipse - then attach to the eclipsed debugger - it is > slow as heck..... > > Any ideas? > > On Monday, August 27, 2012 1:42:00 PM UTC-7, Adam Sas wrote: >> >> Hi, >> >> Recently I experienced the same problem. Have you figured out how to >> solve it? >> >> Best regards >> >> W dniu poniedziałek, 11 kwietnia 2011 15:54:44 UTC+2 użytkownik innusius >> napisał: >>> >>> No breakpoints and it is slow as hell. This is some code issue as I >>> see that after each reload of debug , it takes longer and longer to >>> reload application or maybe it depends of how long it runs... >>> >>> On Apr 7, 6:27 pm, Chris Conroy <[email protected]> wrote: >>> > Eclipse's debug hooks can sometimes cause pathological slowdowns if >>> you have >>> > a breakpoint set on a method entry point. This can happen for regular >>> java >>> > (read: non-GWT) programs as well. Try removing any breakpoints you >>> have set >>> > (or at least, removing any on the method entry--you can set them just >>> fine >>> > on the first line of the function instead) >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > On Wed, Apr 6, 2011 at 3:15 PM, PTJ <[email protected]> wrote: >>> > > Recently I was running my GWT application in devmode via the Eclipse >>> > > plugin in the Google Chrome Browser. Chrome stopped responding and >>> my >>> > > browser completely crashed, requiring me to restart my computer. I >>> > > restarted my computer and tried to run my GWT application again, but >>> > > this time it was SUPER slow. Devmode has always been a little slow, >>> > > but now it's at the point where it is not even usable anymore. The >>> > > weird part is that it is only when running in debug mode via the >>> > > Eclipse plugin, standard run (not debug) via eclipse, the devmode >>> Ant >>> > > target, and production depoyment (WAR) work fine. >>> > >>> > > I have tried to run other GWT applications and now they are all >>> > > running unbearably slow now as well. I uninstalled/reinstalled the >>> > > Google Plugin, upgraded to Eclipse Helios (was using Galileo), >>> > > upgraded to GWT 2.2.0 (was using 2.0.3), etc and nothing has worked. >>> > > I am the only one on my team having this issue and we are all >>> running >>> > > the EXACT same codebase. >>> > >>> > > Has anyone encountered this issue before? Any help would be greatly >>> > > appreciated. I have spent ~2 days straight trying to figure out >>> this >>> > > out! >>> > >>> > > Environment (at this point I have tried a number of different >>> versions >>> > > of the below libraries, all produced the same issue of being too >>> slow >>> > > in devmode debugging via Eclipse): >>> > > -GWT 2.2.0 >>> > > -Eclipse Helios w/ Google Plugin for Eclipse 3.6 & GWT SDK 2.2.0 >>> > > -Google Chrome 10.0.648.204 >>> > > -GXT 2.2.3 (for GWT 2.2) >>> > >>> > > Regards, >>> > > Paul J. >>> > >>> > > -- >>> > > You received this message because you are subscribed to the Google >>> Groups >>> > > "Google Web Toolkit" group. >>> > > To post to this group, send email to [email protected]. >>> > > To unsubscribe from this group, send email to >>> > > [email protected]. >>> > > For more options, visit this group at >>> > >http://groups.google.com/group/google-web-toolkit?hl=en. >> >> -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/RNQA3Q2gGNgJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
