| Memory Leaks ¶ | |
| I tried using some tools to find where my memory leaks are, and they point to hmenu.js. Both Leak.exe and the Leak Monitor extension for FF (https://addons.mozilla.org/firefox/2490/) show leaks. They show them for this site as well. It is difficult to deploy if we end up crashing end users browsers as they take up all the memory. | |
| Re: Memory Leaks ¶ | |
| Just browsing this site seems to leak 1MB per page view. :( | |
| last |
| Re: Memory Leaks ¶ | |
| We carefully tuned DynarchMenu to prevent memory leaks. However, addition of latest features might create some leaks--though I'm not sure. OTOH, on our website we use a lot of other in-house scripts besides DynarchMenu. Those were not designed for IE leaks, so you shouldn't use our website as a reference. I will try to look into it. | |
| last |
| Re[2]: Memory Leaks ¶ | |
| The leaks are happening in FireFox. I think you were one of the first people to figure out the huge IE leaks with closures and COM elements, though there are other types of leaks affect both IE and Firefox. Here is a link at Mozilla: http://www.mozilla.org/scriptable/avoiding-leaks.html That one is the best and most complete description of how JS code leaks. A little over my head, but ought to be great for you! They fixed some small things starting with Mozilla 1.8. Here is the log of the guy that writes the Leak Monitor: http://dbaron.org/mozilla/leak-monitor/ And if you wanted to be real hard core: http://www.mozilla.org/performance/leak-brownbag.html Unfortunately, I see the 1MB per page on our own site with the menus too, and about 30k leak without the menus (I'm working on that one). | |
| last |
| Re[2]: Memory Leaks ¶ | |
| You know, it seems to be mostly a Mozilla/Firefox issue. I don't see near the same amount of leaks in IE, if any. | |
| last |














