News for hackers. Stuff that matters.
Re:This is why memory fragmentation is bad by mcpherrinm on Tuesday July 05, 2011 @01:41AM (#2728779)
What if I have 10 tabs open, each with 5 images that are 10mb each? It's not an unreasonable workload.

Yet there's 500mb, right there. Never? Whatsoever? I don't think so.

Re:This is why memory fragmentation is bad by spicyj on Tuesday July 05, 2011 @01:52AM (#2728799)
I seriously doubt you're opening many pages with 10 MB images; even 1 MB is considered pretty large for a web image.
Re:This is why memory fragmentation is bad by masklinn on Tuesday July 05, 2011 @05:14AM (#2729162)
> even 1 MB is considered pretty large for a web image.

Compressed. Remember that in order to display it, the browser has to unpack it to what amounts to a bitmap. And newer, better compression formats (e.g. PNG) make that even worse in compressing the same bitmap file to a much smaller transmission size.

Re:This is why memory fragmentation is bad by tsvk on Tuesday July 05, 2011 @02:18AM (#2728851)
Did you consider compressed JPG/PNG on disk versus uncompressed raw image data bitmap in RAM?

A 1024x768 32-bit image is 1024x768x4 = 3.145.728 bytes when uncompressed.

Re:This is why memory fragmentation is bad by mcpherrinm on Tuesday July 05, 2011 @02:05AM (#2728831)
Right: the example is contrived. My point is mainly that it is actually within reach, and that workload needs to be taken into consideration when making any statement about how much memory a browser should be using.
Re:This is why memory fragmentation is bad by monkeypizza on Tuesday July 05, 2011 @02:07AM (#2728834)
It happens to me all the time - the "linked images" bookmarklet combined with EarthPorn reddit + autopager.