Milonic provide full featured pull down web menus for some of the worlds largest companies
click here to see what it can do for you

Download Milonic DHTML Menu
Buy Milonic DHTML Menu

Back To Start Of Archive
Taken From The Forum: Archived Topics for the old Version 3.0 JavaScript Menu
Forum Topic: Click to view post
Last Updated: Thursday February 8 2018 - 06:02:43

Memory leak!

Poster: scot.d.thiesmeyer __at__
Dated: Wednesday April 17 2002 - 6:13:40 BST

Anyone else noticed a memory leak while using NS 4.73 on a Windows 2k platform?

I'm working on an intranet site for my company using this wonderful script and just noticed that when NS was left open to the page with the menu on it for an extended period of time, the virtual memory was increased by the OS.

I fortunately have access to several computers and did an experiment and checked the system resources with the page up without activating the menu or any of the other rollovers and watched in horror as the physical memory trickled down at about 24k per second. I allowed one machine to go so far that it acually locked up and had to be rebooted.

This memory leak didn't occur under IE 4.0 .
I do have other scripts on the page, however they didn't cause this anomaly when I removed the menu script.

I'm utilizing version 3.3 of the script (from Dynamic Drive) and love it, but can't keep using it if it can crash the user's workstation.

Any thoughts, ideas, or (one can hope) solutions?


Re: Memory leak!

Poster: yadin
Dated: Thursday April 18 2002 - 3:34:45 BST

Make sure you have the newest release, 3.3.19 as this sounds like an issue we had in earlier versions and have corrected.

Re: Memory leak!

Poster: scotthiesmeyer __at__
Dated: Thursday April 18 2002 - 17:49:17 BST


First off, thanks very much for the reply and for all the hard work you folks do on this script! I'll be sending in my payment for a high-level support contract this week!

I double-checked and am running version 3.3.19 of the script.

One thing I just remembered last night is that IE 5.00 MAY have been running in the background (minimized) on the same page. NS 4.73 was also running on the same machine when the OS adjusted the virtual memory and then crashed and had to be rebooted.

If running both browsers on the same machine on the same page was the only reason for the memory leak, I'm not concerned too much. (What knucklehead runs both browsers at the same time on the same page!?! Oh wait...that was me)

My apologies that I neglected to post that information the first time.

Re: Memory leak!

Poster: Andy
Dated: Thursday April 25 2002 - 16:48:29 BST

I am getting the same thing in Win2k/NS 4.75 with version 3.3.19 of the menu. If I leave NS open for a long period of time it balloons to hundreds of Megabytes of RAM.