Status

()

Toolkit
Password Manager
RESOLVED WORKSFORME
9 years ago
5 years ago

People

(Reporter: dietrich, Unassigned)

Tracking

({dataloss})

Trunk
x86
Windows NT
dataloss
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

9 years ago
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.
(Reporter)

Updated

9 years ago
Keywords: dataloss
Whiteboard: dupeme
Do you still have a signons.sqlite? Is there stuff in it?
Component: General → Password Manager
Product: Firefox → Toolkit
QA Contact: general → password.manager
mconnor noted that mozStorage defaults to "PRAGMA synchronous = NORMAL", we could flip this to = FULL...

http://www.sqlite.org/pragma.html
(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.
Is this bug going anywhere useful at this point? WFM.
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
Last Resolved: 8 years ago
Resolution: --- → WORKSFORME
(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.

Updated

5 years ago
Whiteboard: dupeme
You need to log in before you can comment on or make changes to this bug.