Open Bug 1284938 Opened 6 years ago Updated 1 year ago
Temporary add-ons should not be written to the on-disk database
As mentioned in bug 1209341 comment 0, and several other places, the temporary add-ons added to the database should not written to the on-disk data store. In general, the extensions are still removed after a restart, but it's currently too easy for them to remain after restart when we hit corner cases (e.g., bug 1284439), so it would be safer to just make sure they're never persisted to disk at all.
Per bug 1209341 comment 0 (option #1) is what we decided to implement here, so if temporary add-ons are making it to the JSON store then we're doing something wrong.
Assignee: nobody → rhelmer
Status: NEW → ASSIGNED
I think this might be fixed in the meantime... moving to unconfirmed.
Assignee: rhelmer → nobody
Status: ASSIGNED → UNCONFIRMED
Ever confirmed: false
Severity: normal → S3
Priority: P2 → P3
You need to log in before you can comment on or make changes to this bug.