Linux Flash going to be limited to Chrome

Walter Dnes waltdnes-SLHPyeZ9y/tg9hUCZPvPmw at public.gmane.org
Sun Feb 26 21:16:15 UTC 2012


On Sun, Feb 26, 2012 at 10:08:46AM +1000, Robert Brockway wrote

> I have the same browser resource issues that others are mentioning
> of course.  Maybe it is time to apply for cgroups
> 
> Hmm I wonder what would happen if I got cgroups to limit the brower's
> resource consumption.  Apps are going to have to get better at living
> in an environment in which the OS says 'no' to resource requests
> more often.

  That would kill the browser.  What the browser needs is to set limits
for each individual tab.  As an interim solution, I've taken to blocking
www memory hogs...

1) I don't do Facebook, so I block it in iptables to kill the "like"
button.  The address blocks I know of are...

66.220.144.0/20 66.220.144.0 - 66.220.159.255
69.63.176.0/20 69.63.176.0 - 69.63.191.255
69.171.224.0/19 69.171.224.0 - 69.171.255.255
74.119.76.0/22 74.119.76.0 - 74.119.79.255
173.252.64.0/18 173.252.64.0 - 173.252.127.255
204.15.20.0/22 204.15.20.0 - 204.15.23.255

2) In /etc/hosts, I block a few specific "share" links...
127.0.0.2       edge.sharethis.com
127.0.0.2       platform.twitter.com
127.0.0.2       plusone.google.com

  The websites that you frequent may have different memory hogs.  Use
Firefox about:memory to find out which ones they are.

-- 
Walter Dnes <waltdnes-SLHPyeZ9y/tg9hUCZPvPmw at public.gmane.org>
--
The Toronto Linux Users Group.      Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists





More information about the Legacy mailing list