6 ms·
Same problem here with Safari. I'll vote for process-per-tab as the single best feature of Chrome.
by riobard 16y ago
Same problem here with Safari.
I'll vote for process-per-tab as the single best feature of Chrome.
- redthrowaway 16y agoMe too. The overhead is slightly higher, but having crashes and memory leaks confined to a single tab is awesome.
- mkramlich 16y agoI left Firefox for Safari because Safari was prettier, faster and used less memory. Lately, I'm close to leaving Safari for Chrome because it's faster, uses less memory and crashes less (in fact, it's never crashed so far, vs 100's of times total probably with Safari.) Unfortunately, Chrome is a little uglier, and has certain less user conveniences. So it's not an easy jump to make.
- redthrowaway 16y agoYou think Chrome is ugly and inconvenient? I think it's the best looking browser out there, and the omnibox is fantastic. The only thing I don't like about Chrome on OSX is some flash players don't play nice with it.
- sesqu 16y agoThey're not confined to a single tab for me. It seems like child tabs go in the parent process, for example, so I usually get 2-5 tabs crashing at once. I also get more crashes with Chrome than I used to get with Firefox, but maybe I'm just opening more tabs.
- redthrowaway 16y agoWeird. What OS are you on? On OSX I haven't had a bonafide crash (had a couple tabs hang) in a long time.