Open
Bug 1442747
Opened 6 years ago
Updated 11 months ago
Fix the invalidated container check in test_nsINavHistoryViewer.js
Categories
(Toolkit :: Places, enhancement, P3)
Toolkit
Places
Tracking
()
NEW
People
(Reporter: jakehm, Unassigned)
References
Details
(Keywords: perf, Whiteboard: [sng-scrubbed])
See comment from dependent bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1089691#c36
|
||
Updated•6 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P2
Whiteboard: [fxsearch]
|
|
||
Comment 1•6 years ago
|
||
To add some more details directly here, the test assumed that we were invalidating the whole container thanks to batching, but now we don't batch anymore with RemoveByFilter. We should reintroduce some sort of batching, maybe through the new notifications, or through profiling.
|
||
Updated•2 years ago
|
Severity: normal → S3
|
||
Comment 2•11 months ago
|
||
We need to check the performance of removeByFilter in a batch removal, particularly when the filter is host and optimize using the new Places notifications.
|
||
Updated•11 months ago
|
See Also: → https://mozilla-hub.atlassian.net/browse/SNG-752
You need to log in
before you can comment on or make changes to this bug.
Description
•