Javascript menu leaks memory

[djvalles@yahoo.com webforumsuser@macromedia.com]

We've implemented a hierarchical menu on our web site using Fireworks, but its javascript is leaking memory in IE 6 and other browers on each page refresh.

We're aware that IE 5/6 has some known memory leak issues regarding dynamic HTML, but we also know that the javascript can be fixed somehow to prevent these leaks.

Does anyone know how to repair Firework-generated menu javascript to prevent these memory leaks?

[Murray *TMM*]

Memory leaks aside, there are several other serious problems with these
menus. I cannot in conscience recommend them to anyone, especially
considering that there are much better ways to do these menus that have none
of the problems. Need links to them?

--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver MX
(If you *MUST* email me, don't LAUGH when you do so!)
==================
[url]news://forums.macromedia.com/macromedia.dreamweaver[/url] - THE BEST WAY TO GET
ANSWERS
==================
[url]http://www.dreamweavermx-templates.com[/url] - Template Triage!
[url]http://www.projectseven.com/go[/url] - DW FAQs, Tutorials & Resources
[url]http://www.DreamweaverFAQ.com[/url] - DW FAQs, Tutorials & Resources
[url]http://www.macromedia.com/support/search/[/url] - Macromedia (MM) Technotes
==================

"djvalles@yahoo.com" <webforumsuser@macromedia.com> wrote in message
news:blhi4d$bkf$1@forums.macromedia.com...

> We've implemented a hierarchical menu on our web site using Fireworks, but

its javascript is leaking memory in IE 6 and other browers on each page
refresh.

>
> We're aware that IE 5/6 has some known memory leak issues regarding

dynamic HTML, but we also know that the javascript can be fixed somehow to
prevent these leaks.

>
> Does anyone know how to repair Firework-generated menu javascript to

prevent these memory leaks?

>
>

[djvalles@yahoo.com webforumsuser@macromedia.com]

Yes, please send me the links.

However, if you do know how to correct the memory leak, please tell me - I'm familiar with JS, there's just a lot in there.

Thanks.

[Murray *TMM*]

I couldn't begin to tell you how to fix leaks - in fact I'm taking your word
that they are there. I have never noticed any.

[url]http://www.projectseven.com/tutorials/menuing/mcloser/index.htm[/url]

or

[url]http://www.projectseven.com/tutorials/auto_hide/index.htm[/url]

or even -

[url]http://www.youngpup.net/?request=/components/ypSlideOutMenus.xml[/url]

--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver MX
(If you *MUST* email me, don't LAUGH when you do so!)
==================
[url]news://forums.macromedia.com/macromedia.dreamweaver[/url] - THE BEST WAY TO GET
ANSWERS
==================
[url]http://www.dreamweavermx-templates.com[/url] - Template Triage!
[url]http://www.projectseven.com/go[/url] - DW FAQs, Tutorials & Resources
[url]http://www.DreamweaverFAQ.com[/url] - DW FAQs, Tutorials & Resources
[url]http://www.macromedia.com/support/search/[/url] - Macromedia (MM) Technotes
==================

"djvalles@yahoo.com" <webforumsuser@macromedia.com> wrote in message
news:bli24v$bj8$1@forums.macromedia.com...

> Yes, please send me the links.
>
> However, if you do know how to correct the memory leak, please tell me -

I'm familiar with JS, there's just a lot in there.

>
> Thanks.
>
>

[Richard Cornford]

"djvalles@yahoo.com" <webforumsuser@macromedia.com> wrote in message
news:bli24v$bj8$1@forums.macromedia.com...

> However, if you do know how to correct the memory leak, please
>tell me - I'm familiar with JS, there's just a lot in there.

The memory leaks in IE are caused when DOM elements (and/or ActiveX
objects) hold references to JavaScript objects while those JavaScript
objects hold references to the DOM elements (no matter how indirectly).
The Garbage collector in IE cannot free any objects involved in such a
circular chain of references.

Breaking the circle (at any point) allows the garbage collector to free
the memory, and the onunload event provides a good opportunity to break
the circular references (though not forming them in the first place
would be a better option if that is practical).

I have no intention of looking at any Fireworks menu code ever again (it
is total rubbish) so I could not tell you which references would need to
be nulled. Be suspicious of functions (especially inner functions)
assigned to event handlers, expando properties and uncleared DOM element
references preserved in closures (often accidentally when code is
written by people who do not really understand JavaScript) and check
every DOM element that implements the Element (and possibly Node)
interface(s) (including the document object).

There have been a couple of fairly detailed discussions of this problem
on the comp.lang.javascript newsgroup so a bit a searching at
groups.google.com would produce more detailed information.

Richard.