FormHistory.jsm migration and DB creation should be off the main thread

NEW
Unassigned

Status

()

Toolkit
Form Manager
5 years ago
2 years ago

People

(Reporter: Gavin, Unassigned)

Tracking

(Blocks: 1 bug, {main-thread-io})

Trunk
main-thread-io
Points:
13
Bug Flags:
firefox-backlog +

Firefox Tracking Flags

(Not tracked)

Details

See data in bug 878677 - essentially all of the work under dbInit() in FormHistory.jsm still occurs synchronously on the main thread. We should get rid of that, if possible.
Keywords: main-thread-io

Updated

5 years ago
Blocks: 887887
We should just use openAsyncDatabase and then fix any consumer to be async.
Migration and schema may be funny to handle, though Task.jsm may help handling errors.
The even better alternative may be to switch to Sqlite.jsm, though that may require slightly more refactoring.
Blocks: 950073
Whiteboard: p=0

Updated

4 years ago
No longer blocks: 950073
Flags: firefox-backlog+
Whiteboard: p=0 → p=13

Updated

3 years ago
Points: --- → 13
Whiteboard: p=13
You need to log in before you can comment on or make changes to this bug.