Tabbed Browsing Contains a HUGE Memory Leak

RESOLVED INCOMPLETE

Status

()

--
major
RESOLVED INCOMPLETE
11 years ago
10 years ago

People

(Reporter: nathan.spector, Unassigned)

Tracking

Trunk
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a8) Gecko/2007091216 GranParadiso/3.0a8
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a8) Gecko/2007091216 GranParadiso/3.0a8

Whenever i close a tab, and watch my windows task manager, i have noticed that it doesn't deallocate the memory that i saw allocated for it to begin with.

Reproducible: Always

Steps to Reproduce:
1.open gran paridiso
2.open a bunch of tabs
3.watch memory allocation rise
4.close a bunch
5.watch memory allocation stay the same
Actual Results:  
My computer became slower, and i had to kill gran paradiso.

Expected Results:  
deallocated the memory.

Comment 1

11 years ago
Nathan,

- Can you try with a recent nightly build (say, at most, 3 days old)
- Can you install D. Baron's latest Leak monitor version 3.6
http://dbaron.org/mozilla/leak-monitor/
- Can you specify some of your system resources which may be helpful for this bug; like RAM. There are reasons for requesting such info.
- Can you identify the URLs you visit when you create tabs
- Can you explicit the memory allocation involved in the steps as an example. If you can be precise, this could help.
As stated, "HUGE", "bunch of tabs", "watch memory allocation rise", "a bunch", "slower", etc... are not quantitative values, objective measurements, specific expressions, formalized information which can help in this kind of bug. In the absolute and in the relative, they refer to nothing concrete, actually.
I'm not suggesting that there is no memory leakage; I'm suggesting that, as described, as worded and as posted, your bug report may not as helpful as it can be.
Also, note that this bug may have been already filed too.

Comment 2

11 years ago
Version: Trunk
Version: unspecified → Trunk

Updated

10 years ago
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.