[dba-Tech] the problem was flash, not chrome

[Jim Lawrence]

Thanks for the heads up. :-) 

I have been fighting the Chrome "pig" for a while and had only found that by going into "Task manager", killing the Chrome modules directly, effectively crashing it, then restarting Chrome and allowing it to "restore" its lost links, was my only work-around. Crude, direct, but it is effective and definitely better than closing out properly restarting and losing all your links.  

Jim 

----- Original Message -----
From: "Peter Brawley" <peter.brawley at earthlink.net>
To: "Discussion of Hardware and Software issues" <dba-tech at databaseadvisors.com>
Sent: Sunday, June 14, 2015 10:26:45 AM
Subject: [dba-Tech] the problem was flash, not chrome

On an old geezer of a box running 64-bit Win7Pro in 4G of RAM, with no 
capacity for RAM expansion, Chrome was often eating up to a gigabyte of 
memory /per tab/, inciting swap thrashing. No amount of Chrome tuning 
could dissuade it from such behaviour.

Till I added the "FlashControl" Chrome extension, which immediately made 
the memory problem vanish---no tab now uses even 200KB no matter how 
long it's been open---and also removed the annoyance of unwanted, 
intrusive flash videos launching themselves and disturbing the cherished 
quiet in this room. The tiny price I pay for this boon is that in the 
unlikely event I do wish to play a flash video, I must click on it.

Jes' sayin'.

PB
_______________________________________________
dba-Tech mailing list
dba-Tech at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-tech
Website: http://www.databaseadvisors.com