Closed
Bug 247222
Opened 21 years ago
Closed 21 years ago
memory usage continues to grow while viewing any web site.
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 130157
People
(Reporter: azadi2015, Assigned: bugzilla)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040614 Firefox/0.9
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040614 Firefox/0.9
Using any web page as any example, minimize the window under XP and then
maximize it again. The memory usage jumps to a higher amount. Then continue to
load 3 or 4 more pages one after another. The memory should stay constant.
Minimizing the window again reduces the memory down to the original and
maximizing it again makes the memory jump, but makes it considerably less.
Reproducible: Always
Steps to Reproduce:
1. Open Firefox .9 and view Windows Taks Manager and note memory changing
2. View a few sites to see the memory jump.
3. Minimize and restore to lower memory usage.
Actual Results:
Firefox's memory usage tripled on my machine after following the reproduction
steps and minimizing it reduces it.
Expected Results:
The software should've held a pretty constant memory usage.
Comment 1•21 years ago
|
||
0.9 uses a lot more memory than 0.8 for me.
Especially with multiple tabs open or after it's been running for quite some time.
Flags: blocking1.0? → blocking1.0+
same with Mozilla suite 1.7 fin on WinNT4
Side-effect:
it might crash sometime, when it runs together with OpenOffice 112, which also
uses netscape/mozille-runtime-dlls - but in different versons - and also runs
out of memory.
severity/Prio. should set to higher level soon.
Martin
Comment 3•21 years ago
|
||
(In reply to comment #1)
> 0.9 uses a lot more memory than 0.8 for me.
> Especially with multiple tabs open or after it's been running for quite some time.
Please don't set blocking + flags. Only set ? flags. Changing to blocking-aviary1.0?
Flags: blocking-aviary1.0+ → blocking-aviary1.0?
Comment 4•21 years ago
|
||
(In reply to comment #0)
> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7)
Gecko/20040614 Firefox/0.9
>
> Using any web page as any example, minimize the window under XP and then
> maximize it again. The memory usage jumps to a higher amount. Then continue to
> load 3 or 4 more pages one after another. The memory should stay constant.
> Minimizing the window again reduces the memory down to the original and
> maximizing it again makes the memory jump, but makes it considerably less.
>
> Reproducible: Always
> Steps to Reproduce:
> 1. Open Firefox .9 and view Windows Taks Manager and note memory changing
Although FF is leaking , opening Taskmanager makes things FAR WORSE.
I have noticed this first in Firebird 0.7 (my first experience) and it's still
the case.
Somehow Taskmanager and Firebird/Firefox interact and cause Firefox to slow down
noticably, especially the repainting of screens when changing tabs is bad (from
in-a-flash to seconds). Offcourse you won't notice this on a real fast machine.
I tested it on various Pentiums/Athlons <1400 MHz, and the all show the same
behaviour(all 1Gb mem). Unfortunately I haven't been able to test it on anything
but Win2k.
Tip: don't use taskmanager if you don't want to make things worse.
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040630
Firefox/0.9.0+
Could the slowdown caused by taskman hint in the direction of the problem ?
Updated•21 years ago
|
Flags: blocking-aviary1.0?
Comment 5•21 years ago
|
||
Works for me, even with Task Manager open. Mozilla/5.0 (Windows; U; Windows NT
5.1; en-US; rv:1.7) Gecko/20040624 Firefox/0.9
Can you be more specific and try to pinpoint when this bug occurs? Otherwise,
vague bugs like these get marked as never being fixed or works for me. Also try
searching Bugzilla since there's loads of duplicates and bugs about memory leakage.
Windows that free memory upon minimizing is by OS design (which seems like what
this bug is actually about). I can view any process in Task Manager, and it will
reduce memory usage upon minimizing (and then spring back up when restored).
hey
>hao2lian
well, in could not be a work for you, have a look at the increasing number of
issues related to the searchword "memory"
More to the suite than firefox, of corse, but I guess in this case it is no
difference.
however.
This first open window (right now for bugzilla) gives me a 50 percent cpu-usage,
an while I have 20 windows open, my taskmonitor read 400+ windows-tasks open and
a total of 240 MB memory with 120 MB private, and closing one visible will free
abt 18 invisible.
I guess it would be a good idea to collect all memory-related issues and set
them to started. Mozilla has sideeffects to other applications, and that is a
problem.
rgds
Martin
Comment 7•21 years ago
|
||
mlk keyword?
Comment 8•21 years ago
|
||
*** This bug has been marked as a duplicate of 130157 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•