Linked by Wes Bascas on Wed 3rd Jul 2013 11:00 UTC
Mozilla & Gecko clones Over the weekend, the crew at Tom's Hardware was busy testing the recently-released Firefox 22 using the usual bevy of benchmarks. This roundup included Chrome 27, Firefox 22, IE10, and Opera 12, along with the new Chromium-based build of Opera Next (alos known as Opera 15).
Thread beginning with comment 566287
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: I keep saying...
by Fergy on Thu 4th Jul 2013 21:03 UTC in reply to "RE[4]: I keep saying..."
Fergy
Member since:
2006-04-10

I don't care about what little individual bits and pieces of a browser use. It all adds up, and the end result is what matters. I care what a brand new, clean instance of a browser takes up with no web page open... and it shouldn't be anywhere near 200 MB. That's a whopping 20% of the total memory I have, with no web page even open! That's just ridiculous. Think about that for a second: should a web browser even have to take over 100 MB just to display a blank page? I seriously don't think so.

Sure... you could argue, get rid of the extensions, they take up memory. That only shaves off maybe about 50 MB... and 150 MB is still high. And you're still stuck with a browser hogging an unacceptable amount of memory on its own before you even enter a URL.

So have you looked at about:memory?

Reply Parent Score: 2

RE[6]: I keep saying...
by UltraZelda64 on Thu 4th Jul 2013 22:09 in reply to "RE[5]: I keep saying..."
UltraZelda64 Member since:
2006-12-05

top and htop work perfectly fine to get the measurements I need, but since you insist:

about:memory Explicit Allocations:
185.77 MB (100.0%) -- explicit
...
about:memory Other Measurements:
251.84 MB ── resident
239.42 MB ── resident-unique

htop reading: 238M

So, again, what was the point of going through all that crap and looking through dozens of smaller values when I only care about the grand total--which any system monitor should return accurately? The end result is that the browser itself shows a very similar "total memory usage," and that's what I care about.

Note: The above was measured on a completely fresh copy of Firefox after completely exiting the previous instance. The only difference compared to my previous tests was that I went to "about:config" immediately after running the browser (which was, again, set to start with a blank page) and before taking any measurements, so they should all be in line.

Edited 2013-07-04 22:21 UTC

Reply Parent Score: 2

RE[7]: I keep saying...
by UltraZelda64 on Thu 4th Jul 2013 23:55 in reply to "RE[6]: I keep saying..."
UltraZelda64 Member since:
2006-12-05

Meh... I meant to say that I went to about:memory. I'm so used to following "about:" with "config" it's not even funny.

Reply Parent Score: 2

RE[7]: I keep saying...
by Fergy on Fri 5th Jul 2013 06:43 in reply to "RE[6]: I keep saying..."
Fergy Member since:
2006-04-10

So, again, what was the point of going through all that crap and looking through dozens of smaller values when I only care about the grand total--which any system monitor should return accurately? The end result is that the browser itself shows a very similar "total memory usage," and that's what I care about.

Because you still don't know why it is using that memory.
Mozilla measures memory usage of each build: https://areweslimyet.com/
This is my about:memory: http://pastebin.com/vAZywjmu

Edited 2013-07-05 06:53 UTC

Reply Parent Score: 3

RE[7]: I keep saying...
by zlynx on Fri 5th Jul 2013 18:56 in reply to "RE[6]: I keep saying..."
zlynx Member since:
2005-07-20


So, again, what was the point of going through all that crap and looking through dozens of smaller values when I only care about the grand total--which any system monitor should return accurately? The end result is that the browser itself shows a very similar "total memory usage," and that's what I care about.


For example, when I just ran about:memory on my Firefox it showed me that plus.google.com was using about 55 MB in the browser. I closed that tab and voila, Firefox shrank by about 50 MB.

Almost all of the google web pages are more Javascript application than HTML page and use large amounts of RAM.

Reply Parent Score: 2