Closed
Bug 293618
Opened 19 years ago
Closed 19 years ago
this MHT file causes firefox to get into a memory condition where it starts gobbling up memory
Categories
(Firefox :: File Handling, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: kk, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0 StumbleUpon/1.999 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0 StumbleUpon/1.999 Memory goes off the charts, firefox needs to be killed. Reproducible: Always Steps to Reproduce: 1. Open the mht file with firefox 2. watch your single-core machine get on its knees 3. kill firefox Actual Results: memory usage shoots up, got to over 1GB the first time before I could kill it. Expected Results: fail gracefully if it's a bad file, which I'm note certain it is (works in IE, etc) problem file: http://bs.minimalist.com/mozillabug/CompleteReport.mht working MHT file (much smaller) http://bs.minimalist.com/mozillabug/SummaryReport.mht
Comment 1•19 years ago
|
||
Does it work if you run Firefox in the safemode ? (close ff and click on the Firefox safemode entry in the windows startmenu)
my bad - I guess mozilla/firefox doean't handle the MHT filetype internally? in safe mode when I load the mht, it asks how I Wasnt to open it (mhtfile is the only entry). I choose it, it pops open an Internet Explorer and show it to me there. when I open it in regular mode, firefox opens it directly (shows opening in tabs... dialog) and the memory oscillates between 80M and 800M and eventually it finishes loading while still using 770M of RAM. Based on this, I guess an extension or plugin might be handling it?
Comment 3•19 years ago
|
||
it's an extension if ot works in the safemode. (safemode is just Firefox without extensions) Mozilla doesn't support mhtml Files, see bug 18764 marking invalid (you can't report extension bugs in bugzilla)
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
thank you, sorry for the trouble. i will try to contact the author of the extension, Christopher Ottley, even though there appears to be no conatct info for him.
You need to log in
before you can comment on or make changes to this bug.
Description
•