367173 - Leak on Google Personalized Home with new Firefox profile

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Robert Morton]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1

Google Personalized Home (www.google.com/ig) will cause Firefox v2.0.0.1 to leak memory.

Reproducible: Always

Steps to Reproduce:
1. Create a new profile and launch Firefox.
2. Browse to www.google.com/ig.  Use the default personalized screen (i.e. do not log in to an existing Google account, as the default page is enough to reproduce the leak).

Actual Results:  
Leaked outer window 240bac8 at address 240bac8.
Leaked inner window 283f848 (outer 240bac8) at address 283f848.
 ... with URI "http://www.google.com/ig".
Leaked document at address 23cf258.
 ... with URI "http://www.google.com/ig".
Summary:
Leaked 2 out of 10 DOM Windows
Leaked 1 out of 40 documents
Leaked 0 out of 4 docshells


Expected Results:  
No leaks.

Note that I am using the leak detection tool by David Baron:  http://dbaron.org/log/2006-01#e20060110a

I am indicating that this is a major issue.  I have experienced memory leaks with Firefox for a very long time, but I have been respectful of the developers' time by not posting bugs without detailed information.  This has finally reached a critical point of frustration for me, and I will try to provide as much information as possible.  The significant majority of my leaks are experienced during difficult-to-reproduce circumstances which include a combination of extensions, preferences, and browsing history that would cause a developer to reject the bug despite its seriousness.  Instead I will present low-magnitude leaks such as the above, so that there is no excuse for disregarding pleas for help from users such as myself.  However I expect this to be taken seriously, because otherwise I can have no hope that the other problems I experience will ever be addressed.

Comment 1

[Robert Morton]

Also, please note that I attempted to search for duplicates of this particular issue via: Search -> "Google leak".  There is not enough information in the leak log for me to know how to find duplicates of the same problem, so this may be an area to consider improving such that the community can better assist the developers.

Comment 2

[Alexander Winston]

This looks like a duplicate of Bug 353090

Comment 3

[Robert Morton]

Perhaps it is, and I see your comment on that other bug.  But that bug is marked as Fixed, and the version is the same as reported by Firefox 2.0.0.1.  So either this is a new bug or the existing bug needs to be reopened for further testing and fixes. Unless the other bug gets reopened I presume that this one should stay active.

Comment 4

[u88484]

This bug was reported using a version of Firefox that security and stability updates are no longer provided for.  All users are strongly encouraged to upgrade to Firefox 3 by selecting 'Check for Updates' in the Help menu or by going to http://www.mozilla.com/en-US/firefox/firefox.html

If you can no longer reproduce this bug using the latest Firefox 3.0.x version, please change the status of this bug to 'RESOLVED' 'WORKSFORME'.

If you can still reproduce this bug, please provide additional details to help resolve this issue.

Comment 5

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please reply if you can still reproduce this bug with Firefox 3.5.3 or later in a new profile with the latest plugins (flash, quicktime, java, etc.).