Hi Rob,
It is not problem with RPC -calls ,i.e 16k of memory leak is due to
gwt-components creation.
to avoid this we need to reuse the old references with new state
inspite of creating new objects for every RPC call.
Thanks
-Kiran.Kuppula
On Nov 13, 7:18 pm, Rob wrote:
> I've been trying ou
Oh, eventually windows reports that Chrome has crashed, though
dismissing the error leaves Chrome open (strange). "Developer Tools"/
Scrips shows an error like this every second (the same period as the
RPC timer set up in onModuleLoad() ):
Uncaught Error: Error calling method on NPObject!
On Dec
Sorry, I thought the XMLHttpRequests weren't leaking, but apparently
they still might be.
Here's what I did:
Google Chrome 4.0.249.22 (Development version)
GWT 2.0.0 RC2
Created GWT app: webAppCreator -out MemTest memtest.MemTest
Added this to onModuleLoad():
Timer timer = new Timer() {
Regarding the XMLHttpRequest leak, it seems I just need to wait for
the garbage collector to run. Does anyone know how to manually
initiate garbage collection in Chrome (or in the other browsers, for
that matter)?
On Dec 4, 2:41 pm, mrpantsuit wrote:
> I downloaded the Developer Channel version
I downloaded the Developer Channel version of Chrome, which has some
nice heap analysis developer tools. I thought that perhaps my memory
leaks were not restricted to IE, but were simply more pronounced on
it. Turns out I had several memory leaks.
I changed to use the GWT incubator progress bar
A diff on com.google.gwt.xhr.client.XMLHttpRequest should give you an idea
of what code has changed and when it changed. That said, Rob points out
earlier in this thread that he is not seeing the issue in 1.7.
Are you in a position where you could build your app with RC2 to see if the
leak goes aw
I'm seeing a similar memory leak in 1.7. Does anyone know if this bug
predated 2.0, or was it introduced therein?
On Nov 14, 11:28 am, Rob wrote:
> Seehttp://code.google.com/p/google-web-toolkit/issues/detail?id=4133
> andhttp://code.google.com/p/google-web-toolkit/issues/detail?id=4229
>
> Issu
Yes.
http://code.google.com/p/google-web-toolkit/issues/detail?id=4133
On Nov 13, 8:18 am, Rob wrote:
> I've been trying out one of my existing apps with GWT 2.0 to see what
> advantages it has and have noticed a major memory leak when using RPC
> with Internet Explorer 8.0.
>
> Basically my app
There are over 100 issues that are still 'New' which were reported 2 years
ago or more.
2009/11/14 Rob
Issue 4133 was raised almost a month ago but doesn't seem to have been
> acknowledged yet - would anyone from the GWT team care to comment ?
--
You received this message because you are subs
See http://code.google.com/p/google-web-toolkit/issues/detail?id=4133
and http://code.google.com/p/google-web-toolkit/issues/detail?id=4229
Issue 4133 was raised almost a month ago but doesn't seem to have been
acknowledged yet - would anyone from the GWT team care to comment ?
Cheers
Rob
On Nov
I've been trying out one of my existing apps with GWT 2.0 to see what
advantages it has and have noticed a major memory leak when using RPC
with Internet Explorer 8.0.
Basically my application reads some values from a database and
displays these in the browser every 1 second. I am seeing a memory
11 matches
Mail list logo
