Bug 24935 - Perform rendering in separate processes
Summary: Perform rendering in separate processes
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL: https://bugs.edge.launchpad.net/webki...
Keywords: Gtk
: 24934 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-03-30 09:04 PDT by kxra
Modified: 2012-02-20 14:42 PST (History)
8 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description kxra 2009-03-30 09:04:04 PDT 
I thought this was implemented through the browser itself (like Google Chrome managed to do), but according to the Midori guys, it needs to happen in Webkit. 
http://www.twotoasts.de/bugs/index.php?do=details&task_id=304

Similar to Google Chrome, Midori should separate tabs into separate processes that will not crash the whole browser if one of them freezes.
https://bugs.edge.launchpad.net/webkit-open-source/+bug/343391
Comment 1 Mark Rowe (bdash) 2009-03-30 11:27:06 PDT 
*** Bug 24934 has been marked as a duplicate of this bug. ***
Comment 2 Jeff Fortin 2009-12-19 06:41:37 PST 
Bug 25065 might be a duplicate, or not. It depends whether the webkit devs want to take the one-process-per-tab approach or not.
Comment 3 Martin Robinson 2012-02-20 14:42:58 PST 
This bug is a duplicate of the entire WebKit2 approach. While there is only one WebProcess, eventually it would be nice to have a multiple.