I can believe you'd want 100+ tabs open, but I can't believe that flash wouldn't have forced a crash with even a dozen long running instances, unless you have the build with the new integrated flash plugin.
Chrome does a pretty terrific job of surviving the Flash plugin — it doesn't let it get out of control nearly as much, when it does it only affects a few tabs, and if it dies or I kill it everything's peachy with black boxes where flash once was. It shits the bed a lot more on Linux by a large factor, but Chrome's countermeasures work just the same.
Flash video playback does stutter regularly on my ridiculously overpowered machine. Occasionally a group of tabs will pause from an obviously flash-related issue (the flash open file dialog has been causing me grief), but it recovers in a couple seconds. Once a month or so I have to kill the flash plugin process because it goes on a runaway malloc train, but it doesn't affect my tabsplosion at all — I just have to refresh a couple of them when having flash loaded again would serve some useful purpose.
FF trunk, and now 3.6 (after they backported it), runs all plugins in isolated processes. I can manually killall plugin-container if flash goes nuts (like using over a gig of memory, which I've seen it do).
A lot of the icky problems with having a lot of tabs went away soley due to that (at least, for those without habitual flashblock usage).
Comments
I can believe you'd want 100+ tabs open, but I can't believe that flash wouldn't have forced a crash with even a dozen long running instances, unless you have the build with the new integrated flash plugin.
Chrome does a pretty terrific job of surviving the Flash plugin — it doesn't let it get out of control nearly as much, when it does it only affects a few tabs, and if it dies or I kill it everything's peachy with black boxes where flash once was. It shits the bed a lot more on Linux by a large factor, but Chrome's countermeasures work just the same.
Flash video playback does stutter regularly on my ridiculously overpowered machine. Occasionally a group of tabs will pause from an obviously flash-related issue (the flash open file dialog has been causing me grief), but it recovers in a couple seconds. Once a month or so I have to kill the flash plugin process because it goes on a runaway malloc train, but it doesn't affect my tabsplosion at all — I just have to refresh a couple of them when having flash loaded again would serve some useful purpose.
FF trunk, and now 3.6 (after they backported it), runs all plugins in isolated processes. I can manually killall plugin-container if flash goes nuts (like using over a gig of memory, which I've seen it do).
A lot of the icky problems with having a lot of tabs went away soley due to that (at least, for those without habitual flashblock usage).