3 ms·
Funny, I just switched back to Firefox for development due to the prevalence of tab crashes in Chrome.
by rhizome 15y ago
Funny, I just switched back to Firefox for development due to the prevalence of tab crashes in Chrome.
- darreld 15y agoYup. 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.
- nsmartt 15y agoI'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?
- rhizome 15y agoProcess-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.
- DanielGeisler 15y agoThanks, this could be a valid issue, but so far my CPU and ARM utilization seem to be much less than using Firefox. Well, time will tell.
- rhizome 15y agoThat may be the case, and to be sure I switched to Chrome in the first place due to the lag in having an 800M Firefox process stinking up the joint, so for now my conclusion is that they both suck in subtly different ways, behave identically 80% of the time, and the remainder I'll just bat back and forth with my default browser setting.