Created by Daniel Hable (dthable@bigfoot.com) on Wednesday, April 29, 1998 7:09:23 PM PDT Additional Details : We've been offering support for UW-Madison students and have seen some major problems with Netscape while running the OS in question. After watching the NT Task Manager, we have found that the process netscape.exe keeps requesting memory until about 12000K at which point Netscape crashes ( using 32 MB of RAM.) Numerous messages occur with the lack of Virutal Memory. We are looking for a confirmation on this finding. I already looked at developer.netscape.com and home.netscape.com without finding any whitepapers on the topic. Updated by (blythe@netscape.com) on Tuesday, June 9, 1998 4:19:17 PM PDT Additional Details : Will assign to danm@netscape.com as soon as they add to AssignTo field.

The resolution I'm really looking for is "need more info," but, errr, "won't fix" is almost applicable. Mozilla has a great many memory leaks; the picture changes from day to day. At one point, I had it down to 10 at startup. Today, it has 39 for about 400 bytes. Loading Netscape Netcenter leaks about 20 times again. We shoot some down occasionally; someone makes some more. It's a thing in flux. There are other pages which can eat huge, gaping chunks of memory legitimately. Opening multiple pages and printing can also use a lot of the stuff. If you (dthable) suspect a couple of particular websites as showcasing Mozilla memory leaks particularly dramatically, please add the URL(s) to this report, and re-open the bug. I'm interested in quashing any egregious memory leaks we may have right now. But I don't know of any that stand out above the noise or pose any serious immediate threat. In general, the poor thing is known to suffer from a bunch of small leaks which aren't known to cause any serious harm. We fix them occasionally.

Try the latest mozilla code. Whole new world. Marking Verified/Won't Fix