I just read further down the page: Posted September 4, 2008 at 3:18 pm | Permalink<http://blog.beplacid.net/2008/09/04/tasty-google-chrome-bug-so-much-for-isolated-tabsprocesses/#comment-3192>
This is a way to force a crash for testing purposes. Can't actually call it a bug and it doesn't test the isolated tab process claim as it crashes the Chrome process itself and not one of the tab processes. Still, thanks for posting it, it is an interesting find. So, it's not really a bug, but a feature (for developers to use for debugging). --Don Ellis On Thu, Sep 4, 2008 at 6:31 PM, Don Ellis <[EMAIL PROTECTED]> wrote: > Worked on my copy (crashing, that is ;-) ). But, it restarted instantly, > leaving me where I was before typing the forbidden string. Friendly little > "Whoa! Google Chrome has crashed. Restart now?" dialog pops up instantly, > then when I click "ok", Chrome opens up just like it was. Hold on -- second > time I tried it, got a "restore previous session" option. First time, it was > back up to previous status before I had time to blink. > Nasty crash, but very nice recovery! > > --Don Ellis > > > On Thu, Sep 4, 2008 at 11:34 AM, Mike Bigalke <[EMAIL PROTECTED]>wrote: > >> I haven't tried it myself, since I haven't installed it yet... but can >> anyone verify this? >> >> Type this into a Chrome tab's address bar >> >> :% >> >> Here's the link... >> >> >> http://blog.beplacid.net/2008/09/04/tasty-google-chrome-bug-so-much-for-isolated-tabsprocesses/ >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ Central West End Linux Users Group (via Google Groups) Main page: http://www.cwelug.org To post: [email protected] To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] More options: http://groups.google.com/group/cwelug -~----------~----~----~----~------~----~------~--~---
