437769 - When you close Firefox and open it another time with the start-option "Open last tabs" it sometimes loads a blank page instead of your last tabs

Status: RESOLVED INCOMPLETE

(Firefox :: Session Restore, defect)

Description

[Joeri Boi]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; nl; rv:1.9) Gecko/2008052906 Firefox/3.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; nl; rv:1.9) Gecko/2008052906 Firefox/3.0

I got a dutch Firefox so I don't know the right translation for it; when I open Firefox, I have set it to open my last closed pages/tabs. Sometimes it does not do this and it opens with a blank page.
Also when I first close my browser, then my downloadmanager, bookmarkmanager,... ect, it always opens a blank page instead of my last closed pages/tabs.

Reproducible: Sometimes

Steps to Reproduce:
1.Open an/several internetpage(s)
2.Close Mozilla firefox and shut down your computer
3.Open Mozilla firefox again
Actual Results:  
Blank page instead of my last closed internet page

Expected Results:  
Show my last closed internet page

I'm using Firefox 3 RC2
This was also a problem on Firefox 3 B5 and Firefox 3 RC1
Never had this problem on Firefox 2

Comment 1

[[:Cww]]

You may have not closed Firefox properly and not closed all the windows at the same time, leaving one active window or process when Firefox exited and hence nothing to recover.  Try closing with File > Exit

Comment 2

[Matthias Versen [:Matti]]

Do you use Tabmix plus ?
possible dupe of bug 435055

Comment 3

[Joeri Boi]

Nope, but I haven't noticed the  bug for a few days now. Only it sometimes doesn't warns me when closing multiple tasks, but now I just tried it and it works fine :)

Comment 4

[Yann MERRIEN]

Did you turn off the Preference->Privacy->"always erase my private data"->"always erase my history when closing Firefox" option? 

If it is on, you should ALWAYS start with a blank page, and the solution is just to turn it off.

Comment 5

[Simon Bünzli]

Closing as INCOMPLETE due to lack of answer to comment #4.

Joeri: Please reopen should this issue still exist and not be due to bug 398817.