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/21/2007 12:14:55 PM
List:com.googlegroups.google-gears

It looks like ~100 bytes leaked per page. Does that match what you are seeing?

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

Hi again,

It seems to have something to do with closures in Javascript and how many files that get loaded. I made an extreme test case that loads a single JS file 1000 times and each file generates a class using closures. I verified that it leaks when Google gears is enabled and if I disable it it doesn't leak.

Steps to reproduce: 1. Download the example package.
http://tinymce.moxiecode.com/google/gears_leak.zip 2. Enable Google gears on Windows Vista 64bits in IE 7. 3. Reload the page a few times and watch the memory using the Task manager. 4. Disable Google gears and restart browser. 5. Reload the page a few times and watch that the memory jumps up a bit but then stops i.e. no leak.

Regards

On Sep 21, 12:22 am, "Ben Lisbakken" <lisb@google.com> wrote:

Hey Spocke -

Do you think you could send us your app and give us any instructions to recreate the leak? What OS are you using?

Thanks for posting this for us to investigate! We appreciate your feedback.

-Ben

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

Hi,

Could not find a proper bug report page for google gears so I just fire away here at the groups instead.

Anyway, there is a major memory leak in Google gears. It seems to depend on the script size loaded by the page. First I thought that I was doing something wrong not properly disposing DOM references etc. Then I simply loaded the script with out executing anything and to my amazement it still leaked memory so it couldn't be a DOM/JS reference problem. Also the memory leak didn't show if I used the memory leak tools for IE (Drip and sIEve) probably because they don't load the Google gears addon in their explorer instance.

So I stated disabling "addons" in IE 7 and when I disabled google gears the memory leak was gone. So the conclusion is that Google gears is leaking memory and in my app it was about 200kb each reload.

Regards