I was comparing the memory footprint of it, when I realized it was actually running across several process. At first it looked rather light weight at around 38meg private mem. Then I noticed there was roughly one of those for each tab I had open. It did seem quite responsive though. -j On Tue, Sep 2, 2008 at 12:55 PM, Charles Jones < charles.jones@ciscolearning.org> wrote: > Nadim Hoque wrote: > > Today Google released a new browser called Chrome (www.google.com/chrome). > It is apparently open source or at least has open source components such as > web kit and some Firefox things. Unfortunately it is windows only, but they > are going to release it on Mac and Linux soon, they just want as many people > to try it out. I am using it right now and it seems pretty good. > > I've been watching the development of Chrome with some interest. I don't > think it will become a mainstream browser, but hopefully some of the ideas > that they have implemented will be incorporated into other browsers. I think > one of the best things they did, from both a performance and a security > standpoint, was to make every tab, plugin, etc a seperate jailed process. > This means that if something crashes, it doesn't hork the entire browser, > just that tab. And if something running in a tab is hanging or using lots of > resources, it can be throttled or at least you can now see what it causing > it. And things running in tabs cannot access the memory space of other tabs > or the entire browser. Also, since everything is a process, when you close a > tab it completely frees up the memory it was using, so no memory leaks and > fragmentation like you get with current browsers. > > Hmm that was more than one thing :) > > --------------------------------------------------- > PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us > To subscribe, unsubscribe, or to change your mail settings: > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss > -- Josh | josh@computeristsolutions.com | http://computeristsolutions.com