Convert frecency notifications to a PlacesEvent
Categories
(Toolkit :: Places, task, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox86 | --- | fixed |
People
(Reporter: mak, Assigned: daisuke)
References
Details
Attachments
(6 files, 6 obsolete files)
We have onFrecencyChanged and onManyFrecenciesChanged, the latter is used when it would not make sense to notify changes one by one.
It looks like the single call is only used by NewTabUtils, but considered the small amount of links it's handling it could just use the batched call.
Thus, it looks like we could just introduce frecencies-changed notification, also because we plan to move towards a system where frecency is not calculated immediately, but in chunks on idle.
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 1•4 years ago
|
||
Assignee | ||
Comment 2•4 years ago
|
||
Depends on D99419
Assignee | ||
Comment 3•4 years ago
|
||
Depends on D99420
Assignee | ||
Comment 4•4 years ago
|
||
Depends on D99421
Assignee | ||
Comment 5•4 years ago
|
||
Depends on D99422
Assignee | ||
Comment 6•4 years ago
|
||
Depends on D99423
Assignee | ||
Comment 7•4 years ago
|
||
Assignee | ||
Comment 8•4 years ago
|
||
Depends on D100457
Assignee | ||
Comment 9•4 years ago
|
||
Depends on D100458
Assignee | ||
Comment 10•4 years ago
|
||
Depends on D100459
Assignee | ||
Comment 11•4 years ago
|
||
Depends on D100460
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Comment 12•4 years ago
|
||
Comment 13•4 years ago
|
||
Comment 14•4 years ago
|
||
Backed outfor causing memory leaks.
Backout link: https://hg.mozilla.org/integration/autoland/rev/076223795fcaa7a25cafe6fe2061da7a36fb0d05
Failure log: https://treeherder.mozilla.org/logviewer?job_id=326787342&repo=autoland&lineNumber=3639
Assignee | ||
Comment 15•4 years ago
|
||
Depends on D100461
Assignee | ||
Updated•4 years ago
|
Comment 16•4 years ago
|
||
Comment 17•4 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/9a1d599b4060
https://hg.mozilla.org/mozilla-central/rev/53e385030d67
https://hg.mozilla.org/mozilla-central/rev/2043a28e668e
https://hg.mozilla.org/mozilla-central/rev/0a92dfd99dac
https://hg.mozilla.org/mozilla-central/rev/37b2f438bd2b
https://hg.mozilla.org/mozilla-central/rev/c8b691b8e793
Comment 18•4 years ago
|
||
Backed out 6 changesets (bug 1678619) on suspicion of causing crashes (bug 1687914). a=backout DONTBUILD
Backout link: https://hg.mozilla.org/mozilla-central/rev/8e996166e64e30320578a0980baf62eb6e2247d5
Updated•4 years ago
|
Reporter | ||
Comment 19•4 years ago
|
||
Figuring out the crash may not be trivial.
First of all, we should verify the crash reports go away after the backout.
I'd suggest to split this bug into depdencies.
In the first dependency we can land the conversion from onFrecencyChanged => onManyFrecenciesChanged.
In the second one we can land all the boilerplate code for the new notification, but don't change consumers.
Ideally that allows us to land the biggest chunk of these changes, without hitting the crash, if we hit the crash we know that part is culprit.
The last part will stay in this bug, that is the actual conversion of consumers.
In the meanwhile we can speak with some crash experts (Gabriele Svelto maybe) and some threads magician (asuth or some other core experts?) to figure out where the problem may lay.
Comment 20•4 years ago
|
||
Comment 21•4 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/d275db0c1f78
https://hg.mozilla.org/mozilla-central/rev/6ad0b0a4c2d4
https://hg.mozilla.org/mozilla-central/rev/405847d2ed21
https://hg.mozilla.org/mozilla-central/rev/bb388b59a6dd
https://hg.mozilla.org/mozilla-central/rev/d8ab5dc64a22
https://hg.mozilla.org/mozilla-central/rev/7c1829b47919
Assignee | ||
Updated•4 years ago
|
Description
•