Linked by Thom Holwerda on Wed 9th Jun 2010 20:12 UTC
Thread beginning with comment 429406
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2010-03-08
I agree with the multiprocess thing, myself because I hate seeing a plugin crash leading to loss of data, but as you said it's not part of Webkit itself (making it so is the goal of the Webkit2 project), it's only part of Chrome/Chromium's implementation.
Firefox as a Gecko frontend could just do the same thing and open one new Gecko process per tab without in-depth work on the underlying engine. It'd be a performance nightmare, however, because Gecko has not been optimized for such use at all, hence we'd get 100 MB/tab memory usage and such.
Maybe there would be some incompatibilities with legacy code as well, but usually rendering threads of several tabs should not interfere with each other.
Edited 2010-06-10 09:37 UTC