Closed Bug 21468 Opened 25 years ago Closed 25 years ago

Memory footprint of Mozilla too high (24MB!)

Categories

(SeaMonkey :: UI Design, defect, P3)

x86
Windows NT

Tracking

(Not tracked)

VERIFIED WONTFIX

People

(Reporter: sas, Assigned: don)

References

()

Details

Environment:

Mozilla: M11 NightlyBuild
BuildID: 1999121908
OS: NT 4.0 SP3
PC: HP Vectra VA, Pentium 200MHz, 64MB RAM

How to reproduce:

1. Load URL http://www.slashdot.org/
2. Bring up th "Windows NT Task manager"(using CTL-ATL-DEL and selecting ATL-T)
3. Select "Processes" and check the memory used by Mozilla

What happens:

1. You can see in the "NT Task manager", mozilla is using 24MB
   of memory under memory usage.

PS: Comparision: For the same page:

    Memory usage by Communicator 4.7 + mail :  8MB
    Memory usage by IE 5.0                  :  6MB
    Memory usage by Mozilla M11             : 24MB!

--
-Sas
Reassigning all of leger's unscreened Browser-General bugs to nobody@mozilla.org
for pre-screening and triage.
The (somewhat) good news: it now takes 5 Mozilla browser windows viewing
Slashdot to use up 24MB on NT on a system equivalent to the reporter's
(only difference: a slower processor) with a few other apps running.

The bad news: one window viewing Slashdot still takes up 12MB.

The worse news: Closing four of the five windows viewing Slashdot only
reduces the memory usage from 24MB to 21MB! (Even after starting more apps)

Tested with: 2000-01-01-08-M13 nightly binary on Windows NT 4.0sp3.
Assignee: nobody → don
Component: Browser-General → XPApps
This looks like a Don bug...
We're tracking memory usage on Tinderbox and are
very aware of the memory usage problem.
This general bug isn't very useful, please file specific
bugs per this problem.  marking won't fix; it's not
"invalid", and this bug will just keep sliding out
without meaning very much.

Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WONTFIX
Marking Verified/Won't Fix.
Status: RESOLVED → VERIFIED
Product: Core → Mozilla Application Suite
You need to log in before you can comment on or make changes to this bug.