522424 - Will not keep saved passwords when closed and reopened quickly.

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[mattdel83]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729)

I've noticed a trend since the 3.5.x release, if I accidently close Firefox and reopen it ASAP(which doesn't always happen because Firefox.exe likes to lurk in my process list for a while sometimes, even sometimes requiring a reboot because FF will not reopen with a crashed instance already running), my stored passwords to forums/webmails/etc... anything.. will not work. Subsequently, if you allow a minute or two after closing Firefox, and then reopen, they will work and be cookied like normal.

Also, if I run ANY full screen game that changes my pixel depth, and receive a facebook chat while the game is running as the active process, Firefox crashes and will not reopen for some time, again, usually requiring a reboot.

Reproducible: Always

Steps to Reproduce:
1. Close Firefox via X
2. Immediately reopen
3. Proceed to any page which you've previously stored login information
Actual Results:  
Same thing. Must re-login, Firefox asks me if I wish to change the password, acting as if it knows I have one already but didn't supply it for me.

Expected Results:  
Use the cookie.

Comment 1

[Tyler Downer [He/Him]]

Reporter, are you still seeing this issue with Firefox 3.6.12 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
Also, please consider using the most recent Firefox 4 beta build, your bug may be resolved there.

Comment 2

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.13 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.