Sumit Chandel wrote:
I've seen some cases where IE would blow up when sending overly
complex DTOs through the wire (deep maps or map values referring the
DTO object itself).
Sounds reminiscent of issue 3577.
http://code.google.com/p/google-web-toolkit/issues/detail?id=3577
Ankur,
If I understand correctly, you're describing two separate issues here:
1. The incubator GlassPanel appears to be causing a leak. How did you detect
this?
2. RPC is causing IE's memory usage to increase over time.
Are we talking about OOPHM or web mode in both of these cases? If it's
OOPHM,
hi
Actully we have built the code from the gwt trunk.so the breaking
of code is not done manuallyit is one of the feature of gwt 2.0.
Its true that only our application is running on the browser and the
memory has reached upto 700MB.and out codebase really huge with
lots of
Hi Ankur,
An application size of 3MB sounds extremely large. Is that gzipped or
uncompressed? Also, how large is your codebase?
I would imagine that the runAsync feature would have given you a huge boost
in reducing the initial download size of your application. You mentioned
that you broke down
hi
thanks for the reply.But we checked its not due to image bundle.We are using
a proper workaround that is mensioned in the issue.
Actully main problem what we are facind is due to the listeners.And it being
very difficut to profile the application in debug mode bcoz most of the
refrences are
Hi Ankur,
Could it be that you are using ImageBundle in your application ? We
had similar issues when using ImageBundle, even though we only had a
very small collection of images.
http://code.google.com/p/google-web-toolkit/issues/detail?id=3573
David
On Wed, Jul 22, 2009 at 7:51 PM, ankur
hi joel...do u hav any suggestion regarding this??
On Tue, Jul 21, 2009 at 10:57 PM, ankuur xs4an...@gmail.com wrote:
hi
We are using the gwt 2.0 code from gwt trunk.And we hav seen a drastic
improvement in the page loading especially in case of IE(6 and
7).Actully breaking the compiled
hi
We are using the gwt 2.0 code from gwt trunk.And we hav seen a drastic
improvement in the page loading especially in case of IE(6 and
7).Actully breaking the compiled code into the multiple script tag
did the trick.
But now we are facing the browser memory problem.Actully our total
compiled
