News for hackers. Stuff that matters.
Re:Chrome 27, Firefox 22, IE10, And Opera Next, Benchmarked by ksec on Monday July 01, 2013 @12:41PM (#5971787)
Can you elaborate on that? I am pretty sure those bugs about rendering ( lots ) of images were fix a few versions ago.
Re:Chrome 27, Firefox 22, IE10, And Opera Next, Benchmarked by bri3d on Monday July 01, 2013 @01:59PM (#5972416)
It looks like they tried to land a patch which would discard images that were outside of the viewport, but it broke so they backed it out of FF 22 ( https://bugzilla.mozilla.org/show_bug.cgi?id=872235 ). Then, there's https://bugzilla.mozilla.org/show_bug.cgi?id=847223 where all downloaded images are decoded and live forever regardless of if they are shown.
Re:Chrome 27, Firefox 22, IE10, And Opera Next, Benchmarked by nnethercote on Tuesday July 02, 2013 @11:20PM (#5982261)
The backed-out-of-FF22 patch has been fixed and is present and enabled in FF24 (currently in Aurora).

> all downloaded images are decoded and live forever regardless of if they are shown.

Nope. Before the backed-out-of-FF22 patch landed, all images in a page were decoded and kept in memory as long as that page was in the foreground. But if you switched to another tab, the decoded images would be discarded.

With the backed-out-of-FF22 patch in place, most images that are downloaded are decoded temporarily, but those that aren't visible are discarded quickly.

When bug 847223 is done, the not-visible images won't even be decoded on page loading.

So, to summarize: in FF24, on image-heavy pages you'll see a memory spike on first load, but it'll quickly drop down. And once bug 847223 is done (hopefully soon, though these things are hard to predict), you won't even see that spike.