Originally Posted by pgans
It makes sense in a perfect world that you'd want it in one process. However, having the multi-process benefits in 2 ways. 1. If you crash a tab, only that tab crashes. Same goes for any plug-ins that page is currently using. 2. Memory leakage is greatly reduced. When you close a tab, ALL of the memory is immediately reclaimed for use by whatever process needs it next. So basically you have a little more upfront memory usage, but better overall. JMO.
I believe that IE8 will go the same route, and also the upcoming Firefox 3.1.
I've experienced many times (and again a few minutes ago) a single tab crashing inside IE7 forcing me to kill the entire process. It's frustrating, but luckily this time I wasn't typing up a long winded post or email in yahoo...
And your explanation of the memory leakage and recovery upon closure makes sense. It makes me wish I had more of an applied knowledge of this kind of stuff so I wouldn't ask what some may consider stupid questions.
One more question about Chrome and such...
I've built a few webpages in the past, simple as they may have been (really nothing more than HTML, only used PHP for timestamping and very basic MySQL functions), they worked for what they were intended.
The question is, when I built these pages in the past, I noticed that IE is much more forgiving than FF when it comes to proper coding. Does anyone know if Chrome is more like FF or IE in this respect?
For my own use, I prefer the more strict coding rules of FF, but hate surfing with FF when someone else has only tested a page with IE.