On Fri, Sep 17, 2010 at 12:33 PM, Michael Kelley <kelley.pixelactive3d.com@gmail.com> wrote:
Speaking of other browsers, has anyone successfully gotten a GWT
plugin for Firefox 4.0 to work?
On Sep 16, 10:13 am, PhilBeaudoin <philippe.beaud...@gmail.com> wrote:
> I echo these thoughts. Chrome is easily my favorite browser for
> everything but testing my GWT apps in dev mode.
>
> On Sep 16, 6:04 am, Sean <slough...@gmail.com> wrote:
>
>
>
> > I'm not sure if this deserves it's own post either, but I can't stand
> > using Chrome in dev mode because when Debugging Chrome constantly
> > informs me that the plugin has stopped responding and do I want to
> > kill it. Is there anyway to say Don't Tell Me Again for the rest of
> > this page's session? Or for this address? Something?
>
> > On Sep 15, 8:33 pm, Michael Kelley
>
> > <kelley.pixelactive3d....@gmail.com> wrote:
> > > I have a WebGL application as well that is very slow in development
> > > mode. Serialization takes minutes in development mode while it takes
> > > seconds in compiled mode.
>
> > > On Sep 15, 9:13 am, "efs@2010" <edwinfsm...@gmail.com> wrote:
>
> > > > I would like to echo the sentiment of this request and in a similar
> > > > vein (and maybe this deserves a separate post) there is also an issue
> > > > with the performance of Chrome in compiled mode in the following
> > > > scenario:
>
> > > > I am using WebGL and when creating very large Float32Arrays (of maybe
> > > > 90,000 elements) it takes an exceptionally long time. I am creating
> > > > only a few of these large arrays and it is instantaneous in Firefox
> > > > (less than two seconds as I would expect) but takes 8 minutes(!) in
> > > > the latest version of Chrome (and all previous versions). One thing
> > > > that I observe during these 8 minutes is that the page fault rate
> > > > (Windows XP) is about 160,000 page faults per second (for the entire 8
> > > > minutes) for the Chrome process and the VMSize is going up and down
> > > > all the time (varying from say 40MB to 50MB) instead of growing
> > > > monotonically. It certainly seems to be some kind of O(n*n) problem
> > > > and maybe even the garbage collector could be running as each element
> > > > of the array is allocated? I don't know.
>
> > > > Any ideas?
>
> > > > Thanks, Ed
>
> > > > On Sep 15, 6:34 am, Brian <hibr...@gmail.com> wrote:
>
> > > > > Can Chrome be made faster in development mode?
>
> > > > > I use Chrome as my default browser as I really like the development
> > > > > tools, but it's slow with gwt development mode. On a table cell,
> > > > > there's a click handler. The click handler displays a popup built
> > > > > with UIBinder. In development mode with Chrome (v 7.0.517.5), it
> > > > > takes approx 3 seconds from click to seeing the popup. With Firefox
> > > > > (3.5.11) it's 'almost' instant -- fast enough anyway that it's not a
> > > > > performance issue.
>
> > > > > In Web Mode with everything compiled, Chrome is super fast again, no
> > > > > issues at all. The perf loss is only in Dev mode.
>
> > > > > Any ideas? Should I switch over to the production branch of chrome
> > > > > (and thus lose speed tracer)?
>
> > > > > -Brian
--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
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 post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
No comments:
Post a Comment