294867 - memory leak flooding mem and causing hang (not responding) since 1.0.4

Status: RESOLVED WONTFIX

(Firefox :: General, defect)

Description

[Navid Zamani]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

this happens nearly every time i open sites with some more media (like a gallery
of panorama-images. but i even got it after opening some random pages as tabs
from a google search.
a plugin automatically restores the tabs, so after restarting firefox i have to
manually stop loading or close them to prevent it from crashing again.
this happened not one time with 1.0.3 for weeks of extensive usage.

it always starts with slowing my whole system. firefox then starts to eat up 99%
cpu and memory usage becomes bigger and bigger. now it can't redraw hs window
anymore. (normally i kill it before it gets an mem overflow error).

additionally i can trigger it by opening Extras->Extensions. (wich never opens.
even if i try it 2 or 3 times)

Reproducible: Always

Steps to Reproduce:
1. go to a site with many embedded (img/plugins) stuff OR open Extras->Extensions
2. open your task manager and watch mem-/cpu-usage for 30-60 sec
3. try to force window-redrawing of firefox

Actual Results:  
Firefox window not responding.
CPU @ 99% for firefox.
MEM @ ~200MB for firefox.

Expected Results:  
Load and display the page OR Show extensions window

I can't get a list of my plugins, but i think this could possibly matter...
(don't know how to get the list elsewhere.)

Comment 1

[Kevin Brosnan]

Please recheck with a current nightly a lot of work has been done on Firefox's
memory usage bug 131456 was one of the bigger fixes.
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/

Comment 2

[Navid Zamani]

is it secure to take a nightly? i mean: are they tested enough for stability?
dont't want to get out of the frying pan into the fire. ;)

i'm just trying with all plugins disabled. i will update you after some more
usage...
i think it's bettersearch because i saw it requesting thumbnails just before it
died...
but this is just an assumption.

Comment 3

[Kevin Brosnan]

Well that is up to you to decide, if you have any concerns it might be better if
you did not. 

The 1.0.x versions of Firefox have not had any core improvements (like memory
handling) since August '04. Which make 1.0.x releases poor canidates for
reporting this type of bug. 

If you don't want to persue this into nighly builds then you or I could close
out the bug as worksforme.

Comment 4

[Navid Zamani]

/me disabled some probably evil extensions and is waiting for some memory
cleanup in firefox. (important thing, that!! ;)

feel free to change it to WORKSFORME, but i call it a WONTFIX because it isn't
fixed and with a closed bug it will not fix itself from nothing. ;)