Closed Bug 341447 Opened 18 years ago Closed 17 years ago

Opening Firefox with about:blank and closing leaks memory

Categories

(Firefox :: General, defect)

x86
Linux
defect
Not set
minor

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: mwu, Unassigned)

References

()

Details

(Keywords: memory-leak)

To reproduce:

1. Close Firefox if opened.
2. Open about:blank in Firefox, either through homepage setting or commandline (eg. ./firefox about:blank)
3. Close Firefox

With a debug build on either trunk or branch, we leak quite a lot:

nsStringStats
 => mAllocCount:          14774
 => mReallocCount:         3247
 => mFreeCount:           12211  --  LEAKED 2563 !!!
 => mShareCount:          14365
 => mAdoptCount:           1781
 => mAdoptFreeCount:       1744  --  LEAKED 37 !!!

leak-gauge.pl says:

Summary:
Leaked 6 out of 6 DOM Windows
Leaked 28 out of 32 documents
Leaked 0 out of 3 docshells

This bug goes away if the user just browses away from about:blank, so it isn't a very big deal, but it is rather odd..
I wonder if my patch in bug 338360 "fixes" this... it removes an "optimization" that makes about:blank startups not load everything immediately.
Bug 39238?
This works for me in a build with the latest patch from bug 383269. Michael, can you confirm?
Looks okay on trunk now.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.