Closed
Bug 1223099
Opened 9 years ago
Closed 9 years ago
Don't accidentally initialize BrowserDB during application:willFinishLaunchingWithOptions
Categories
(Firefox for iOS :: Data Storage, defect)
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
fxios | 1.2+ | --- |
People
(Reporter: rnewman, Assigned: rnewman)
Details
Attachments
(1 file)
See Bug 1223017.
We grab profile.history in order to invalidate the top sites cache… but that involves doing all of the table init for BrowserTable and perhaps checkpointing the WAL.
My proposed fix is to have SQLiteHistory flag itself during init.
Assignee | ||
Comment 1•9 years ago
|
||
Attachment #8685017 -
Flags: review?(sleroux)
Updated•9 years ago
|
Attachment #8685017 -
Flags: review?(sleroux) → review+
Assignee | ||
Comment 2•9 years ago
|
||
c2b2c2c
Assignee | ||
Comment 3•9 years ago
|
||
bnicholson spotted some really weird behavior caused by this commit. Inlining the method call fixed it:
02491fc
You need to log in
before you can comment on or make changes to this bug.
Description
•