crashes if I restore session after I Clear private data on startup

RESOLVED INCOMPLETE

Status

()

Toolkit
Places
--
critical
RESOLVED INCOMPLETE
10 years ago
2 years ago

People

(Reporter: Micah Seneshen, Unassigned)

Tracking

1.9.0 Branch
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: closeme 2009-07-14)

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008051206 Firefox/3.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008051206 Firefox/3.0

I was doing the known bug 
"Deleting an entry from the history sidebar, then invoking the Clear Private Data tool can result Firefox crashing"
(bug 426275)
then it crashed. But then, When I started Firefox 3, i cleared private data. Then i restored the session. I cleared then restored 3 times, and it kept saying,"Mozilla has encountered a problem and needs to close. We are sorry for the inconvenience."

Reproducible: Always

Steps to Reproduce:
1.On startup,clear private data.
2.Restore session.
3.It crashes.
Actual Results:  
It says ,"Mozilla has encountered a problem and needs to close. We are sorry for the inconvenience."

Expected Results:  
Opened the browser window.

I just updated to Windows Service Pack 3.
FF 3: Works fine for me but now I have no option to restore previous session or start new session. I will try again later and file a new bug ticket if necessary.

Comment 2

10 years ago
-> Firefox:General as this might be more related to Places than to Session Restore.
Component: Session Restore → General
QA Contact: session.restore → general

Comment 3

8 years ago
can you reproduce with v3.5? 
 http://www.mozilla.com/en-US/firefox/all-beta.html
Component: General → Places
Product: Firefox → Toolkit
QA Contact: general → places
Whiteboard: closeme 2009-07-14
Version: unspecified → 1.9.0 Branch
No reply, INCO. Please reopen if this happens in Firefox 3.5.1 or later in a new profile.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.