Well, since FF doesn't separate processes...I can't see what your point is.
I never said it did
I never said it did
FireFox now runs the plugins in a separate process just like Chrome and it's causing problems as well as an increase in memory usage just like Chrome that's my point.
Meaning, you don't have browser crashes in IE ? Since it has sandboxed both plugins and tabs before everyone else, I'd argue it's a useful thing.
Especially with poorly programmed Flash games (but that's the dev's fault, not Adobe's)
I don't use IE it just sits there. It's too slow, lacking in features, ugly, clunky, nothing good I can say about it. So as a result I don't use it and don't know if it would crash. I do know Opera, FireFox, Safari, and Camino never crash for me. Chrome doesn't crash often but it crashes more than the others combined for me.
Well, since FF doesn't separate processes...I can't see what your point is.
What planet are you on? FireFox certainly does separate processes. How can you discuss this intelligently if you don't even know the basic facts?
FireFox now runs the plugins in a separate process just like Chrome and it's causing problems as well as an increase in memory usage just like Chrome that's my point.
I do apologise i was commenting on my own ff. Iv not upgraded to 3.6* yet
What planet are you on? FireFox certainly does separate processes. How can you discuss this intelligently if you don't even know the basic facts?
Firefox does not have a multi-process architecture, except for Flash, Silverlight and QuickTime which are all sandboxed.
Firefox does not have a multi-process architecture, except for Flash, Silverlight and QuickTime which are all sandboxed.
They run in a separate process just like Chrome. Chrome also separates the extensions and that's in Firefox's future plans.
Your talking in circles. Since FireFox 3.6 the plugins have run in a separate process. This is the path Chrome has taken and the result is an increase in memory usage. What are you talking about and what is your point?
I'm talking about separating tabs, not only processes. This is what IE has been doing since IE 8.
I'm talking about separating tabs, not only processes. This is what IE has been doing since IE 8.
No FireFox doesn't do that yet and I never said it did. It's heading that way though. Chrome does it and it's memory hog.
Well, Firefox can't (at least not on my system) release memory when you close a tab. Having a one-process-per-tab architecture fixes that, at the expense of using a bit more memory for each tab.
Besides, the only wasted RAM is unused RAM.