Open
Bug 699618
Opened 13 years ago
Updated 2 years ago
Unpack content-prefs.sqlite from omni.jar when profile is created
Categories
(Toolkit :: Preferences, defect)
Toolkit
Preferences
Tracking
()
NEW
People
(Reporter: vladan, Unassigned)
References
Details
(Keywords: perf)
Attachments
(1 file)
|
2.66 KB,
patch
|
Details | Diff | Splinter Review |
To improve first run performance, we will be unpacking pre-created SQLite databases from omni.jar on profile initialization (see bug 691268).
This change extracts content-prefs.sqlite from omni.jar when the database doesn't exist. The extracted DB contains the DB schema but no rows. If extraction fails for whatever reason, an error is logged and the DB is created from scratch as before.
|
Reporter | |
Updated•13 years ago
|
Attachment #571811 -
Attachment is patch: true
|
|
Reporter | |
Updated•13 years ago
|
|
|
Reporter | |
Updated•13 years ago
|
Assignee: nobody → vdjeric
|
|
Reporter | |
Updated•13 years ago
|
Attachment #571811 -
Flags: review?(dtownsend)
|
||
Updated•13 years ago
|
Attachment #571811 -
Flags: review?(dtownsend)
|
||
Comment 1•12 years ago
|
||
Vladan, it is my understanding that we decided to pick another strategy. Should this bug be closed?
Flags: needinfo?(vdjeric)
|
|
Reporter | |
Comment 2•12 years ago
|
||
Flags: needinfo?(vdjeric)
|
|
Reporter | |
Updated•9 years ago
|
Assignee: vladan.bugzilla → nobody
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•