Closed
Bug 1677969
Opened 5 years ago
Closed 5 years ago
Places Expiration should not run a query on startup
Categories
(Toolkit :: Places, enhancement, P3)
Toolkit
Places
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox85 | --- | fixed |
People
(Reporter: mak, Assigned: mak)
References
Details
Attachments
(1 file)
This runs as soon as the service is inited
https://searchfox.org/mozilla-central/rev/277ab3925eae21b419167a34624ec0ab518d0c94/toolkit/components/places/PlacesExpiration.jsm#843-846
I think this is not necessary, we can make it lazier
| Assignee | ||
Comment 1•5 years ago
|
||
Also from the logs in Bug 1675461 it looks like notify is starting sooner than expected, and in the middle of responsiveness tests. We should use idle better.
Bug 1475582 is probably also relevant.
See Also: → 1475582
| Assignee | ||
Comment 2•5 years ago
|
||
Don't run queries immediately when reading prefs on startup, rather use a lazy
getter when necessary.
Wrap the whole notify call in the idle callback.
Use the concurrent promiseDBConnection to read page counts, so it doesn't block.
Use withConnectionWrapper to address the missing shutdown blocker when
expiration runs.
Pushed by mak77@bonardo.net:
https://hg.mozilla.org/integration/autoland/rev/91656bfde225
Places Expiration should not run queries on startup. r=adw
Comment 4•5 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox85:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 85 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•