Searching history show "No results" first before showing results.
Categories
(Firefox :: Firefox View, defect, P2)
Tracking
()
People
(Reporter: jrmuizel, Assigned: jsudiaman)
References
Details
(Whiteboard: [fidefe-firefox-view])
Attachments
(3 files)
STR: Search in history for "youtube"
A page comes up with No results for “youtube” and then I wait longer and the results come up.
Also, even after the results show up it sometimes switches back to the "No results" page. I can't reliably reproduce this though.
Comment 1•2 years ago
|
||
I'm not able to reproduce this on 125.0a1. Jeff, do you know what version of Nightly you were on when you saw this? Does it happen the first time you go to firefox view after starting a new session or sporadically after you've already been to firefox view a few times?
| Reporter | ||
Comment 2•2 years ago
|
||
It happens every time. I've attached a screen recording of me reproducing it in Nightly from 2024-03-04
I have a large history because I've set places.history.expiration.max_pages=9999999 but I imagine you should be able to reproduce by running on slower hardware or artificially delaying the time it takes to get results back.
| Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Comment 3•2 years ago
|
||
Hey Jeff. Thanks for reporting this!
I haven't been able to reproduce the issue despite setting the following as you've done: places.history.expiration.max_pages=9999999
Are you able to run Firefox Profiler? Hopefully that will glean some more info on why this is happening for you. Thanks!
| Reporter | ||
Comment 4•2 years ago
|
||
Sure here's a profile: https://share.firefox.dev/3TPjWb5
I've included the sqlite threads so you can see the time that's spent query the database.
| Reporter | ||
Comment 5•2 years ago
|
||
It doesn't seem like:
https://searchfox.org/mozilla-central/rev/47a0a01e1f7ad0451c6ba6c790d5c6855df512c1/browser/components/firefoxview/fxview-tab-list.mjs#391
checks if there's an active search query happening. Could that be the problem?
Comment 6•2 years ago
|
||
Comment 8•2 years ago
|
||
| bugherder | ||
| Assignee | ||
Comment 9•2 years ago
|
||
I've seen this come up again by simulating a slowdown of the db query. Bug 1887220 - Rework map computations in history should make it easier to catch race conditions, I'll take a look.
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Comment 10•2 years ago
|
||
Comment 11•2 years ago
|
||
(In reply to Jonathan Sudiaman [:jsudiaman] from comment #9)
I've seen this come up again by simulating a slowdown of the db query. Bug 1887220 - Rework map computations in history should make it easier to catch race conditions, I'll take a look.
Just a note that generally we don't re-open older bugs especially if they've already been "shipped". This makes it harder for tracking regressions (knowing when fixes actually landed) and potentially more difficult if uplifts are required for fixes as it won't be as clear for release drivers.
Updated•2 years ago
|
Updated•2 years ago
|
Comment 12•2 years ago
|
||
Comment 13•2 years ago
|
||
| bugherder | ||
Description
•