Closed Bug 407624 Opened 13 years ago Closed 13 years ago

memory leak

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
major

Tracking

()

RESOLVED INVALID

People

(Reporter: henew, Unassigned)

Details

User-Agent:       Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.0.3705; .NET CLR 1.1.4322; Media Center PC 4.0; .NET CLR 2.0.50727)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; pl; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11

when i'd opened few windows with few tabs each, i'd checked how much memory does it takes, because i'd found my computer works really slow, then i'd started to close tab by tab, window by window, until there was only one tab in one window left, and it was just www.google.com, but memory used was still big as I saw in Task Manager, after close the last window everything was fine, but I think it would be very useful if You could fix this problem, cause many times I had to save abd then close all tabs with all windows with important pages for me to turn it on again,  thanks

Reproducible: Always

Steps to Reproduce:
1.close all windows
2.
3.
This bug report is too general to lead to a fix.  If you want to help out with memory usage, grab a trunk build and play around with the tools from http://wiki.mozilla.org/Performance:Leak_Tools to see if you can spot actual object leaks.  Looking at Task Manager numbers isn't especially useful because of fragmentation (see bug 130157 or http://blog.pavlov.net/2007/11/10/memory-fragmentation/).
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.