Firefox doesn't ask to save login data only on SoundCloud after a crash
I was browsing and then I click on private window and quickly moved to the non private window and close it. This always crashes my Firefox and sometimes I lost data (addons prefernces or configs, and saved logins). Now this time I lost all my saved logins and it dones't prompt or ask to save the log in from SoundCloud. The exception list is empty. I'ts really bugging to type in the log in data everytime.
I already tried with safe mode and deleting all the cache.
Any help would be apppreciated.
Thanks.
Izmjenjeno
Svi odgovori (7)
Do theses crashes also happen if you use the Firefox version from the Mozilla server?
Do you have a logins.json or logins.json.corrupt file and key4.db or key3.db in the profile folder?
You can use the button on the "Help -> Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the about:profiles page.
- Help -> Troubleshooting Information -> Profile Directory:
Windows: Show Folder; Linux: Open Directory; Mac: Show in Finder - http://kb.mozillazine.org/Profile_folder_-_Firefox
cor-el said
Do theses crashes also happen if you use the Firefox version from the Mozilla server? Do you have a logins.json or logins.json.corrupt file and key4.db or key3.db in the profile folder? You can use the button on the "Help -> Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the about:profiles page.I
- Help -> Troubleshooting Information -> Profile Directory:
Windows: Show Folder; Linux: Open Directory; Mac: Show in Finder- http://kb.mozillazine.org/Profile_folder_-_Firefox
I have login logins.json.corrup, key4.db and key3.db
What's next now?
Does the logins.json.corrupt file OK if you compare it with a valid logins.json file?
Can the builtin SON viewer parse (expand) this file if you rename it to logins.json or is the file really corrupted?
If you haven't changed the master password recently and logins.json is valid JSON then you can try to rename logins.json.corrupt to logins.json. If that doesn't work then rename key4.db to key4.db.old to make Firefox use key3.db in case key.db is corrupted.
If you keep getting this issue then make sure to backup logins.json and key4.db and other files in the profile folder, so you can recover.
cor-el said
Does the logins.json.corrupt file OK if you compare it with a valid logins.json file? Can the builtin SON viewer parse (expand) this file if you rename it to logins.json or is the file really corrupted? If you haven't changed the master password recently and logins.json is valid JSON then you can try to rename logins.json.corrupt to logins.json. If that doesn't work then rename key4.db to key4.db.old to make Firefox use key3.db in case key.db is corrupted. If you keep getting this issue then make sure to backup logins.json and key4.db and other files in the profile folder, so you can recover.
Sorry to bring this up but I tried this and it didn't work. I'm currently using the lastest stable version of Firefox.
??????? anybody?
Is the logins.json.corrupt file a valid JSON file if you open it in a Firefox tab and use the builtin SON viewer?
Did you try the logins.json.corrupt after a rename to logins.json with both key3.db and key4.db with only one of the key files present?
Note that Firefox needs to switch from profile storage (regular mode) to in-memory storage (PB mode), so switching and closing windows rapidly may not be a good choice in case Firefox is still busy with setting up storage.