Hi,<br> No I have not used open layers before. My experiment was conducted on the open layer's main website. There is a working demonstration on the main page of the website. I would love to give the latest release of open layers a go though. :)
<br><br>Cheers,<br>Wayne<br><br><div><span class="gmail_quote">On 4/11/07, <b class="gmail_sendername">Schuyler Erle</b> <<a href="mailto:sderle@metacarta.com">sderle@metacarta.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Tue, 2007-04-10 at 10:24 -0400, Stephen Woodbridge wrote:<br>> Wei Yang Ng wrote:<br>> > Hi,<br>> > I am a ka-maps user. Recently, I noticed memory leaks (I used Process<br>> > Explorer for windows) in FF2 while navigating maps in my ka-map
<br>> > application. I decided to conduct the same test with Google maps and<br>> > found similar results. The memory does get released if refresh the page,<br>> > however there is some evidence of leaks caused by circular references in
<br>> > Javascript as not all page memory is released as the page refreshes. I<br>> > then decided to conduct the same test with the OpenLayers demo found in<br>> > the main page of the website. Again, I noticed the same problem.
<br>> > Example, FF2's memory usage is 66 mb when i first view the map. As I<br>> > zoom in and out, the usage keeps jumping till I had about 200 mb of<br>> > memory consumed by FF2. Has anyone noticed such a problem?
<br>><br>> Yes, I have noticed something similar. I periodically have to kill FF2<br>> and restart it to regain memory when I have browser open running OL.<br><br>Are you running the 2.4 release candidate? We've done a ton of work on
<br>fixing memory leaks quite recently.<br><br>SDE<br><br></blockquote></div><br>