Comment 14 for bug 270429

i tried to repro this and could only confirm this issue with my working profile, but not in a clean profile.
what i did:
1. create a new profile using 3.0.1
2. save a password for google.com
3. run 3.0.2 (build5) on the same profile
-> password was still available

so i tought it may be caused by an extension, but as an further test i repeated above steps with installing those extension one-by-one to 3.0.1 prior to testing the profile with 3.0.2