*** Bug 69858 has been marked as a duplicate of this bug. ***
Same thing on Windows/i386, build id 2001022105. Ran it for 30minutes on the referenced URL and Mozilla went from a mem. usage of 19000k to 32000k according to Task Manager. Hitting 'stop' or going to another URL halted the climbing usage. Sorry about the dupe by the way.
Just tried this with linux build 2001-02-26-08 and I see a rise in memory usage of about 500k after 40 minutes of the jpeg refreshing continuously. This is not very much.... Brian, do you still see this in a new build?
I am unable to test on Linux ATM (catching a ride to the airport in 15 minutes), but testing on Windows 2000 shows the leak still being there. Build ID 2001022705 Results: Start browser - 19,500K 5 minutes - 21,708K 15 minutes - 23,636K 20 minutes - 24,208K 25 minutes - 24,848K 30 minutes - 25,752K -- hit stop button, load this bug's Bugzilla entry, wait -- 35 minutes - 25,152K As you can see, memory usage is rising by an avg. of somewhere around [6-8]00K/5min after initial loading of the test page. After stopping the browser and changing URLs the memory usage in fact decreases a bit and does not rise at all, thus leading me to still be suspicious of the MJPG. Would go test on Linux, but as I said, must catch a ride to the airport.
updating component and setting default owner
Assignee: asa → pnunn
Status: UNCONFIRMED → NEW
Component: Browser-General → ImageLib
Ever confirmed: true
QA Contact: doronr → tpreston
All pnunn bugs reassigned to Pav, who is taking over the imglib.
Assignee: pnunn → pavlov
Status: ASSIGNED → NEW
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → FIXED
Okay, marking verified
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.