Process-per-tab is supposed to cut down on single tabs taking down the whole browser, but in Chrome's case it just means that Flash will crash daily requiring you to reboot/reload tabs you didn't even know were running Flash. That is, process-per-tab falls down a bit when the thing that crashes is running in multiple tabs anyway.
Comments
Yup. Me too. I'm tired of Chrome's flakiness and process per tab as well as process per plugin. Back to FireFox as default browser.
I'm confused as to why it matters if there's a different process for each plugin/tab. Care to elaborate? Also, what flakiness have you experienced?
Process-per-tab is supposed to cut down on single tabs taking down the whole browser, but in Chrome's case it just means that Flash will crash daily requiring you to reboot/reload tabs you didn't even know were running Flash. That is, process-per-tab falls down a bit when the thing that crashes is running in multiple tabs anyway.