Chrome already has multiple (many) processes. If a process were running when Chrome crashes that does nothing more than display a new window (instantly) "Chrom

Chrome already has multiple (many) processes. If a process were running when Chrome crashes that does nothing more than display a new window (instantly) "Chrome is still running even though it's crashed. Since you didn't ask to close your private windows, would you like to reopen them now? If you do not reopen them they will be lost forever [Keep browsing] [Exit]? "? Who said anything about "disk"? Or, what, it is impossible for Chrome to make two different programs that don't both crash at the same time? It would be different if I asked it to account for the state that power goes out. I just want it to deal with the state that I didn't intend to close a session - that it should still be going but the browser crashed. Finally, what do you think about adding a password functionality, so that typing a password can enable you to reopen the exact session associated with that password? Then it could be saved to disk at the user's request, password-protected. For example I would use this after I have opened many documents for reading, to ensure that if the whole session crashes then I can recover it with a password, from a list that shows only the date of the session and when it ended. That would surely be sufficient, no? Especially if you are allowed to delete these "saved" but password-protected sessions. but, really, I don't need this. Power loss isn't what makes me lose these sessions: Chrome crashing, by itself and unprompted, is what does. so another process that keeps things still in-memory and immediately pops up saying it is still running and allowing me to continue, is more than enough. >Use bookmark folders and delete them when you're done. RIGHT! Like this: http://i.imgur.com/lQOiuEs.png http://i.imgur.com/lQOiuEs.png Where I make a folder called "delete if no crash". In other words: "Folder! Important future work for me: delete this folder if Chrome does NOT fuck up and crash. The reason for this folder is just as a Contingency in CASE Chrome fucks up and crashes". And then manually have a subfolder for each window, because it is not possible to save a set of folders for every open window, just the tabs in the current window. Is it really fair to make the user manually save a folder in case Chrome decides NOT TO DO ITS ONE JOB which is displaying web pages without crashing? Displaying a web page without crashing is the minimum viable product for Chrome. That is its most basic, essential job. I shouldn't have to figure out how to manually work around it not being able to do its most essential function. Of course, in 95% of cases it's great. that's why I use it. Please allow me to select "actually, keep doing your job! don't exit yet" to pop up when the Browser suddenly stops functioning as hard as when a kernel panic or blue screen of death brings down the operating system. I'm not the one "using it wrong" for not manually making contingencies for the browser fucking up.