14 messages in com.googlegroups.google-gearsRe: [google-gears] Re: Google gears l...
FromSent OnAttachments
Spocke20 Sep 2007 14:00 
Ben Lisbakken20 Sep 2007 15:22 
Spocke21 Sep 2007 01:47 
Chris Prince21 Sep 2007 12:14 
Aaron Boodman21 Sep 2007 12:16 
Zachary Kuznia21 Sep 2007 12:23 
Aaron Boodman21 Sep 2007 12:35 
Zachary Kuznia21 Sep 2007 15:22 
Spocke22 Sep 2007 23:39 
Chris Prince22 Sep 2007 23:44 
Spocke22 Sep 2007 23:45 
Michael Nordman24 Sep 2007 14:47 
Spocke26 Sep 2007 01:39 
Chris Prince26 Sep 2007 09:18 
Subject:Re: [google-gears] Re: Google gears leaks memory in IE7 on Vista.
From:Chris Prince (cpri@google.com)
Date:09/26/2007 09:18:56 AM
List:com.googlegroups.google-gears

Cool. Thanks for digging into the problem. Nice investigative work!

On 9/26/07, Spocke <spo@gmail.com> wrote:

I've confirmed that this bug doesn't happen in the 0.2.x versions. But it do occur on the official 0.1.x version currently available. So I guess this bug is resolved and will not be a problem in the future when the 0.2.x branch gets official.

On Sep 24, 11:47 pm, "Michael Nordman" <mich@google.com> wrote:

Thanx for the test case... there was a significant http handler related memory leak in 0.1.x that has been fixed in 0.2.x and newer... i'll compare before and after and see what i see On 9/22/07, Spocke <spo@gmail.com> wrote:

I did some more testing this time on a Windows XP Pro machine and IE 6. Same problem here it leaks a few MBs but not as much as on the Vista machine but stil a lot.

What I found out was that you need to load it through a web server. It doesn't show up if you load it as a local file but when I placed it on my local IIS server it started leaking.

Maybe some gears components only gets injected to the page if you are on a site like the cross domain XHR?

Check if you guys can reproduce it now with the new instructions?

Regards

On Sep 23, 8:39 am, Spocke <spo@gmail.com> wrote:

No, the leak I see is several MB each reload on the attached test case so on my machine it's serious. If I sit and develop my app for a few hours I need to close down the browser since it leaks a few hundred MBs and goes slower and slower. But if I disable google gears it just leaks a few bytes here and there and I guess thats normal explorer leakage. :)

I guess large JS frameworks will have a similar problem. Like Dojo, YUI etc since it seems to depend on the number of JS files included.

If I minimize my application and reduce the number of requests it leaks less. But it still leaks. It's like each JS file with it's source intact remains in the memory.

Could it be some a bug in some specific google gears version. How do I determine the version installed on my computer?

Btw, I run a 64 bits version of Vista could that be a problem some 32/64 bit incompatibility? I've seen other applications behave strangely on my 64 bits OS.

/Spocke

On Sep 22, 12:22 am, "Zachary Kuznia" <z.@google.com> wrote:

Spocke,

What is the magnitude of the increase in the memory footprint you're seeing? I've managed to reproduce the behavior I saw earlier without Gears installed... Both cases grow on average a couple KB per refresh; i.e. I'm not seeing any change with Gears installed.

-Zach

On 9/21/07, Aaron Boodman <a.@google.com> wrote:

AJAX heavy sites can average several requests per minute, so this will be an issue. Obviously not a blocker, but something we should look into.

I suspect the http intercept code leaks?

- a

On 9/21/07, Zachary Kuznia <z.@google.com> wrote:

Yes, per request. The page sources a .js file 1000 times via

script

tags.

-Zach

On 9/21/07, Aaron Boodman <a.@google.com > wrote:

On 9/21/07, Chris Prince <cpri@google.com > wrote:

It looks like ~100 bytes leaked per page. Does that match

what you

are

seeing?

That's per-request, not per-page, right?

- a