I tested this on Maemo again by killing the child process. I get the same result. What I did: - I set http://nu.nl as the custom home page - I opened up the terminal, did "sudo gainroot", then "ps" to view the list of processes. - I then used "kill ****" to kill the PID of the plugin-container process. - I got the crash dialog and tapped on "Close tab" Expected result: - about:home should be getting loaded, because the custom home page crashed. Actual result: - I get a blank page, but with the old page title still in there of the crashed tab. - Another interesting note (maybe). When I open up a new tab, then return to the crashed tab, then suddenly the http://nu.nl page is loading in there. I also noted that no crash report ids are being generated when killing the plugin-container process. Shouldn't I get a crash report id in about:crashes? I don't know how to kill the plugin-container process on Android. If someone would know how to do that, then I could try this out on Android.
You'll want to install ted's addon that has a button to crash the content process.
Ted's "Crash me now!" extension can be installed from here: http://ted.mielczarek.org/mozilla/crashme-new.xpi It can also be downloaded from here: http://code.google.com/p/crashme/ (this one is the place where it gets updated periodically) Note that because of bug 611403, you can't actually install that extension (should be fixed in tomorrow's build).
Note btw, this is a follow-up from bug 619875.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.