Closed
Bug 519466
Opened 15 years ago
Closed 14 years ago
lost all passwords
Categories
(Toolkit :: Password Manager, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: dietrich, Unassigned)
Details
(Keywords: dataloss)
using trunk nightlies, i've lost all passwords a couple of times in the last week (or thereabouts). i've had a few crashes during that time. i have no STR at the moment, just wanted to get this on the radar.
Comment 1•15 years ago
|
||
Do you still have a signons.sqlite? Is there stuff in it?
Component: General → Password Manager
Product: Firefox → Toolkit
QA Contact: general → password.manager
Comment 2•15 years ago
|
||
mconnor noted that mozStorage defaults to "PRAGMA synchronous = NORMAL", we could flip this to = FULL... http://www.sqlite.org/pragma.html
Comment 3•15 years ago
|
||
(In reply to comment #2) > mconnor noted that mozStorage defaults to "PRAGMA synchronous = NORMAL", we > could flip this to = FULL... Mine is set to FULL. That could be because mine is the original signons.sqlite and maybe we hadn't set synchronous=normal yet? > http://www.sqlite.org/pragma.html That seems to imply that pragma only really helps with OS crashes. It also says FULL is slower. Right now that's not an issue, but with more writes happening in bug 465636, it might? Though signons.sqlite is tiny compared to places, so its likely negligible.
Comment 4•14 years ago
|
||
Is this bug going anywhere useful at this point? WFM.
Comment 5•14 years ago
|
||
My new signons db is still synchronous = full (which doesn't really make sense). Either way, it doesn't seem like this has been much of an issue since it came up
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Comment 6•14 years ago
|
||
(In reply to comment #5) > My new signons db is still synchronous = full (which doesn't really make > sense). FWIW, I now know that PRAGMA synchronous is set on each connection, so when I was opening my db via the command line, that was sqlite3 setting synchronous = full, not firefox.
You need to log in
before you can comment on or make changes to this bug.
Description
•