To be clear, it boils down to extra overhead imposed by the multi-process architecture in Chrome. We're looking into ways to optimize this, but it may take a while. If you're using a mac, you can always try debugging in WebKit nightlies, which are like Chrome to a first approximation.
On Thu, Dec 10, 2009 at 9:48 AM, Scott Blum <[email protected]> wrote: > Right now, the Chrome plugin is painfully slow, unfortunately. I suspect > if you try Firefox you'll get a much faster load. > > > On Thu, Dec 10, 2009 at 5:49 AM, gedw99 <[email protected]> wrote: > >> Am using the new 2.0 version. >> >> When i run in debugging mode in eclipse & chrome, its takes about 3 >> minutes to finalise starting up. >> >> is this normal ? >> >> Ged >> >> -- >> http://groups.google.com/group/Google-Web-Toolkit-Contributors >> > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
