279355 - >170MB memory on startup because of master password

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Oliver Mueller]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

I use an automatic proxy URL to get my proxy settings. The .pac file is
protected by an .htaccess. So when I start my firefox, the first thing that
happens is, that it ask for my master password in order to get the login and
password information for the .htaccess and to retrieve the proxy information.

At the point of time the master password request pops up, my firefox uses >170MB
of REALMEM. By now nothing could have been loaded. No window is open, the proxy
setting are not loaded and I removed all my extensions a long time before.

When I turn of the proxy URL and turn it to direct connect, so no master
password popup comes up, the REALMEM (not VMEM) usage is about 30 MB.

This is reproducable every time I switch between the proxy settings.

Reproducible: Always

Steps to Reproduce:
1. Activate master password
2. Enter proxy URL, which must be protected by an HTACCESS
3. Restart firefox

Actual Results:  
memory consumption >170MB

Expected Results:  
not consume more the 40MB of memory

Comment 1

[Oliver Mueller]

Attachment: MacOS X Activity monitor after starting mozilla

Comment 2

[Oliver Mueller]

Attachment: Firefox startup with direct internet connection and without master password

Comment 3

[Oliver Mueller]

The same bug is also on a windows firefox 1.02 version.

As soon as a master password window OR .htaccess window opens memomy jumps up to
200 MB.

Comment 4

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 5

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.