is also consuming a
ridiculous amount of memory. IE9 is a lot better, except that that one is
leaking in RPC due to a bug in JS eval, specifically to IE9 only.
David
On Tue, May 14, 2013 at 2:40 PM, Borys Zibrov
boris.b...@gmail.comjavascript:
wrote:
Yeah, I now it is faster, I just wish
Hi!
We've got an application on GWT 2.5.0 + GXT 3.0.4 with one main page,
containing a big table (like Excel) and a couple of heavy popups
(implemented using GXT Windows).
It works reasonably good at Chrome, FF, and IE9 but is incredibly slow in
IE8.
Memory consumption on opening the main
Yeah, I now it is faster, I just wish there was something I could do
On Tuesday, May 14, 2013 2:39:51 PM UTC+3, Jens wrote:
IE8 is just a different beast than IE9. As IE9 is a lot faster than IE8 I
would guess they changed a lot internally and these changes also account
for the memory
Hi, all!
I've got a fairly complex RIA application involving GWT 2.5 and GXT 3.0.1,
and I noticed that changing compiler flags (like optimization level)
doesn't improve (and even degrades) performance in IE8.
So, could anyone help me out: what are the best compiler settings for
performance in
