Currently our multiprocess architecture lets the browser keep going when one of its tabs crash, but why can't we keep the tabs going when the browser crashes?
At a high level, imagine we had a watchdog process that kept track, essentially, of the tab model and the navigation controllers. When the browser process crashes, we could use this information to do something like session restore, but instead of reloading the tabs from the network, we could re-attach to the tab processes that are already running. There's some trickiness revolving around in-flight requests from the renderer processes to the browser process (such as synchronous XMLHttpRequests), but that seems like a solvable problem. Basically, the approach would be to respond to any in-flight requests with "failure" messages. Thoughts? Adam -- Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
