259850 - Firefox allocating 30MB or more memory to a random plugin

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[RSpliet]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20040914 Firefox/0.10
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20040914 Firefox/0.10

When browsing with Mozilla Firefox, Firefox allocates about 40MB to
libjavaplugin_oji.so. This without having to use the java plugin actually (for
instance on www.google.com). Sometimes this amount is even larger.
Last time this was the same, but with libasound.so



Reproducible: Always
Steps to Reproduce:
1. Start Firefox
2. Browse to google.com (and perhaps around between www.tweakers.net and
google.com, as in my case. Both sites do not use Java, tweakers.net might use
Shockwave Flash)
3. Start gnome-system-monitor
4. Rightclick on the 'firefox-bin' entry and choose memory "division"? (using
Dutch Gnome, it's "geheugenverdeling")

Actual Results:  
libjavaplugin_oji.so (or any other random plugin, for instance libasound.so) has
about 40MB of memory assigned, in 4 part (4x10240KB), without this plugin being
used.

Expected Results:  
Not assign these amounts of memory to unused plugins.

I make use of the Tabbrowser extension, MFF 1.0PR1, and Fedora Core 2 on Gnome.

Comment 1

[RSpliet]

I wish to add that when disabling the TBE, and chmodding the plugins dir to 000,
this problem still occurs. The only difference is that the 10240k memory blocks
doesn't get assigned to one of the plugins in the plugins dir, but to a
different library (.so).

Comment 2

[RSpliet]

Attachment: Example of memory leak

Shows several blocks of 10240K being addressed to rather random plugin

Comment 3

[RSpliet]

Attachment: Example of memory leak 2

Shows an amount of 10240K blocks of memory assigned to random plugins,
different from the other image. All that changed is that this is a different FF
session.

Comment 4

[RSpliet]

Leak still exists in 0.10.1

Comment 5

[RSpliet]

Firefox 1.0 (final) still has this problem, it even looks like it got worse.

Comment 6

[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 7

[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.