Closed Bug 220952 Opened 21 years ago Closed 19 years ago

Virtual memory continues to increase with use; page faults intolerable when restoring window.

Categories

(SeaMonkey :: General, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: markjl, Unassigned)

References

Details

Attachments

(1 file)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030827
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030827

As I continue to use Mozilla, the Virtual Memory usage continues to increase. 
Sometimes, it does go down a bit but, overall, it increases.

If I "minimize" the page and do other things, when I "restore", it takes an
intolerable amount of time because of hundreds of page faults.

I have been running an instance of Mozilla for several days.  According to
TaskInfo2002, the total Virtual Memory in use currently (as I write this) is
368,840 KB; the Fault Count is 315,398.

Firebird seems to behave the same.

Thank you.


Reproducible: Always

Steps to Reproduce:
1.
2.
3.
the page faults after a window-restore is bug 76831
Depends on: 76831
see related Bug 158317
Product: Browser → Seamonkey
I wish to report the following data:

I'm running Windows XP SP2 with NO virtual memory, in a system with 1GB of RAM.
I'm using Mozilla 1.8b, and I'm measuring the memory usage through the "private
bytes" column of Process Explorer (www.sysinternals.com).

After having used Mozilla on and off for a few days for browsing and reading
mail, without closing it, I closed all tabs of the browser window except one, in
which I entered the URL "about:blank". I also closed the mail window and cleared
the cache in the preferences. The only Mozilla window that was left was the one
showing "about:blank". After this, Process Manager indicated a use of 174472
kbytes by Mozilla. Minimizing Mozilla made only a very slight change in this
figure. I then closed Mozilla and started it again, and again opened
"about:blank" in a single tab of a browser window. The memory usage indication
given by Process Explorer was then 17588 kbytes.

I think this is a clear indication of some memory management problem in Mozilla.
For some special reasons, I don't use virtual memory in my system. This behavior
of Mozilla means that I have to close it and restart it every few days, to
prevent it from eating up too much RAM.
According to TaskInfo2003 (see attached), my Firefox is currently using:
     InMem KB:	85,228
   Private KB: 126,436
     Total KB: 474,124

Seems like a lot to me, and it doesn't seem to ever go down by much.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: