Chrome, Firefox Rein In Memory-Hogging Websites

Megalith

Megalith

24-bit/48kHz
Staff member
Joined
Aug 20, 2006
Messages
13,000
Chrome and Firefox are gaining new features that will reduce the amount of memory and resources used. The former is introducing “Page Lifecycle interface,” which will “pause websites that aren't active and reconstitute them when you need them,” while the latter will shave 7MB off each computing process the browser uses (typically hundreds) to draw a website with “Fission Memshrink.” Mozilla is also introducing “site isolation” to its browser: like Chrome, it increases security by isolating code from different sites in different processes.

Fission Memshrink is designed to reduce memory usage, but it might be a wash since Firefox will use more processes. But those processes deliver performance and security improvements that otherwise would gobble up more memory, so it's not unfair to see the glass as half full here. "Project Fission ... will result in more responsiveness. We also expect security benefits from more isolation of different web content," Mozilla said in a statement.
 
Pretty awesome. Doesn't effect me but not everyone has 16GB of memory.

I wonder, for those of us that have more memory than we ever need, does the PLI actually give users a worse experience? I wonder if it can be disabled for the Ram overkill crowd.
 
When running on current FF there is already an extension called "auto tab discard" which really pauses/suspends a tab after X min (you set amount), so when it paused when you click on it, it refreshes tab.
I think it does same as Chrome one is doing.
 
  • Like
Reactions: Meeho
like this
EdKiefer said:
When running on current FF there is already an extension called "auto tab discard" which really pauses/suspends a tab after X min (you set amount), so when it paused when you click on it, it refreshes tab.
I think it does same as Chrome one is doing.
Click to expand...
Depends if the chrome one saves the state of textboxes and so on.

Edit: it seems to be an API for web developers to add in to their pages to save/restore data, so that'd be different from just reloading the page (and quicker).
 
-=SOF=-WID99 said:
would some one tech megalith to spell ? please ?

REIN? ..FFS sake its REIGN in english
Click to expand...

rein
[rān]
NOUN
(reins)
  1. a long, narrow strap attached at one end to a horse's bit, typically used in pairs to guide or check a horse while riding or driving.
VERB
  1. check or guide (a horse) by pulling on its reins.
    "he reined in his horse and waited for her"
Perhaps you should stop critiquing others usage of English and work on your own. Original post is correct. Also, I think you would ask someone to "teach" him to spell, not "tech" him.

Sorry, nothing is more amusing to me than someone attacking someone else for their grammar with gaping holes in their own.
 
Last edited:
Yeah, I don't think he looked too hard at that link he posted :)

Usage
The correct idiomatic phrase is a free rein, not a free reign; see rein
 
ZeqOBpf6 said:
Pretty awesome. Doesn't effect me but not everyone has 16GB of memory.

I wonder, for those of us that have more memory than we ever need, does the PLI actually give users a worse experience? I wonder if it can be disabled for the Ram overkill crowd.
Click to expand...
LOL you act like 16 gigs is a lot of memory. I had 16 gigs all the way back in 2011 and have had 32 gigs now for 2 years. And even now I can use up all that memory with enough tabs no problem if hitting some of those memory hungry sites.
 
-=SOF=-WID99 said:
would some one tech megalith to spell ? please ?

REIN? ..FFS sake its REIGN in english

https://en.oxforddictionaries.com/definition/reign
Click to expand...

As shown above, "rein" was correct.

1: It is "teach" not "tech"
2: Sentences start with capitals.
3: There is no space in front of punctuation.
4: It is "it's" not "its".
5: "Someone" is one word.
6: "For F#cks Sake sake". Really?
7: You capitalize letters at the beginning of the names of people and places.


Stones and glasshouse and all that jazz.

-- edit --
Appended point 7.
 
Last edited:
Gala-own-goal.gif
 
misterbobby said:
LOL you act like 16 gigs is a lot of memory. I had 16 gigs all the way back in 2011 and have had 32 gigs now for 2 years. And even now I can use up all that memory with enough tabs no problem if hitting some of those memory hungry sites.
Click to expand...

Remember that each and every tab is it's own process now, and every process needs to carry the Win32/Win64 APIs along for the ride. Site Isolation is the biggest memory hog in modern browsers; there's a reason why memory usage jumped the second it was implemented.
 
i only keep a few pages open at any one time.. unlike some.. good gawd.. they have so many you can barely see the tabs they are so small LOL
 
You must log in or register to reply here.
Back
Top