Confirmed users
3,816
edits
QA/Firefox3.5/TestPlan/BetaPreview/MocoTestday/SessionRestore: Difference between revisions
Jump to navigation
Jump to search
QA/Firefox3.5/TestPlan/BetaPreview/MocoTestday/SessionRestore (view source)
Revision as of 03:38, 10 June 2009
, 10 June 2009no edit summary
No edit summary |
|||
| Line 1: | Line 1: | ||
The new session restore page allows you to choose which pages and windows to restore after a crash. Previously, we just restored everything all at once, but if one of those pages was the one causing the crash, then this would create a crash | The new session restore page allows you to choose which pages and windows to restore after a crash. Previously, we just restored everything all at once, but if one of those pages was the one causing the crash, then this would create a crash every time you restarted your browser. The page will load in the first tab after a crash and it looks like: | ||
[[File:Picture_3.png]] | |||
To choose to not restore a page or a window, clear the checkmark on the left side of the window. One more note about the way it works - you only see the nifty dialog if you crash '''twice'''. The thinking here is that after the first crash, you just want to bring everything back the way it was. If we crash twice then we know that something is amiss, and maybe one of the open sites is causing the crash so the dialog displays as your first tab. | To choose to not restore a page or a window, clear the checkmark on the left side of the window. One more note about the way it works - you only see the nifty dialog if you crash '''twice'''. The thinking here is that after the first crash, you just want to bring everything back the way it was. If we crash twice then we know that something is amiss, and maybe one of the open sites is causing the crash so the dialog displays as your first tab. | ||
= Causing crashes = | = Causing crashes = | ||
* There used to be a nifty extension that would crash | * There used to be a nifty extension that would crash Firefox on demand. I can't seem to locate it anymore, link anyone? I think Ted owned it... | ||
* You can also open up a terminal window in | * You can also open up a terminal window in Linux and mac and run the following commands: | ||
# ps -A |grep firefox --> displays a list of process ID numbers that correspond to the running instance of Firefox. | # ps -A |grep firefox --> displays a list of process ID numbers that correspond to the running instance of Firefox. | ||
# kill -9 <pid> --> give it the number for the | # kill -9 <pid> --> give it the number for the Firefox instance you want to kill. | ||
* On OS X, you can use Activity Monitor to do a "Force Quit" on the browser. | * On OS X, you can use Activity Monitor to do a "Force Quit" on the browser. | ||
* You can use the Task Manager in Windows to "End Process" the | * You can use the Task Manager in Windows to "End Process" the firefox.exe process. | ||
* You can browse through our currently open [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Core&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=crash+testcase&bug_status=UNCONFIRMED&bug_status=NEW&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=-6m&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= crash bugs] and see if any of the | * You can browse through our currently open [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Core&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=crash+testcase&bug_status=UNCONFIRMED&bug_status=NEW&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=-6m&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= crash bugs] and see if any of the test cases there still crash 3.5 beta 99 (and please leave a note if they do). | ||
= Ideas to Test = | = Ideas to Test = | ||