Closed Bug 547588 Opened 15 years ago Closed 14 years ago

crash in private mode [@ StrChrIA ]

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 627238

People

(Reporter: nightsoul.blackps, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 What about if the browser is crashing in private mode ( i had this problem today and lost all the info) how do you restore the tabs and windows? oh well you can't , this is a bug that i think it must be fixed,it the browser is crashing in private mode you can't restore the window,you will lose all the information,that's why this must be changed the data to be erased when you close the browser,and to keep it in history until then , as if you get a crash your **Dead**.. Reproducible: Always
6643a67b-f2ef-4022-b927-4ddaf2100221
Summary: crash in private mode → crash in private mode [@ StrChrIA ]
Summary: crash in private mode [@ StrChrIA ] → crash in private mode
yes i have seen it,it's a virus?
that's the same id. please leave the subject alone
Summary: crash in private mode → crash in private mode [@ StrChrIA ]
Do you mind sharing the steps to reproduce the problem with us?
Sorry can't remember the steps to reproduce it...
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles You can also try to reproduce in Firefox 4 Beta 8 or later, there are many improvements in the new version, http://www.mozilla.com/en-US/firefox/all-beta.html
Whiteboard: [CLOSEME 2011-1-30]
reporter please confirm that you have the module in bug 627238
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Whiteboard: [CLOSEME 2011-1-30]
You need to log in before you can comment on or make changes to this bug.