close long time memory use

RESOLVED INCOMPLETE

Status

()

RESOLVED INCOMPLETE
10 years ago
10 years ago

People

(Reporter: jlhs5, Unassigned)

Tracking

3.0 Branch
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1

When i try Close Firefox and the memory use is greater than 400MB and time use is more 24 Hours, its not close and process not down of 200MB use, i wait a long time(20 min) but not close PC Especifications 
Core 2 Duo 2GHz
3 GB Ram
250GB HD Free Space 120GB
and my Lap too
Centrino 1.8GHz
1GB ram
80GB HD Free Space 6GB

Reproducible: Always

Steps to Reproduce:
1.Open Firefox Use Normally for a long time 
2.Return to next day and verify memory use is >400MB
3.Try Close and Wait...... after kill Process :D 
Actual Results:  
3 times 2 PC and same results hang


about:buildconfig

Build platform
target
i686-pc-mingw32

Build tools
Compiler 	Version 	Compiler flags
cl 	14.00.50727.762 	-GL -wd4624 -wd4952 -TC -nologo -W3 -Gy -Fd$(PDBFILE)
cl 	14.00.50727.762 	-GR- -GL -wd4624 -wd4952 -TP -nologo -Zc:wchar_t- -W3 -Gy -Fd$(PDBFILE)

Configure arguments
--enable-application=browser --enable-update-channel=release --enable-optimize --disable-debug --disable-tests --enable-update-packaging --enable-official-branding --enable-jemalloc --with-crashreporter-enable-percent=25
(Reporter)

Updated

10 years ago
Version: unspecified → 3.0 Branch

Comment 1

10 years ago
This bug report isn't specific enough to be useful.  Memory use is complicated to debug.  For an overview of the scope of the issue, see http://blog.pavlov.net/2008/03/11/firefox-3-memory-usage/.

For memory use or memory leak bug reports to be useful, they need at least one of the following:

* Steps to reproduce that are specific enough that we can actually see the problem ourselves.

* Debugging output that clearly shows what objects are being leaked or held too long.  (See https://wiki.mozilla.org/Performance:Leak_Tools.  Start with leak-gauge, I guess.)

In your case, since shutdown is taking a long time, an alternative would be to get a profile showing what is going on during shutdown.  But I don't know an easy way to do that on Windows.
some fixes in this area appear in beta 4 and eventually in beta 5. For now this is incomplete
http://www.mozilla.com/en-US/firefox/all-beta.html
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.