Quote: Originally Posted by win7en
Oh, I got it! Each extension installed in Chrome seems to correspond to an independent active process! Which is a stupid "process" in my mind!
It does seem weird to people that are used to firefox or safari, but it works out better for you in the end. You'll find that flash and java also get there own chrome process. People that have used firefox will tell you that when any part of firefox or flash stops responding, then entire program crashes. In Chrome, when a plug-in, add-on or page chrashes, just that one thing chrashes and the rest keeps going just fine. When a page crashes, all you have to do is refresh that page or when something like flash crashes, all the pages stay open, but anything requiring flash stops working until you refresh that page. In firefox (older versions at least, I believe in 4.0 they are switching to chromes way of doing things) if flash crashes, the entire program crashes. Same thing with extensions/plug-ins (or what ever FF calls them). Some are made by amatuers and are pretty unstable. When one crashes, the entire program goes with it because it is all kept in one process.