The Assistant remains stuck in infinite loading after a request is made from a quick prompt in a continued conversation
Categories
(Core :: Machine Learning: Frontend, defect, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox-esr140 | --- | unaffected |
| firefox147 | --- | unaffected |
| firefox148 | --- | unaffected |
| firefox149 | --- | verified |
| firefox150 | --- | verified |
People
(Reporter: rdoghi, Assigned: Mardak)
References
(Blocks 2 open bugs, Regression)
Details
(Keywords: regression, Whiteboard: [genai][chat])
Attachments
(2 files)
Found in
- Nightly 149.0a1 (2026-02-13)
Affected versions
- Nightly 149.0a1 (2026-02-13)
Affected platforms
- all
Steps to reproduce
- Open the Smart Window.
- Ask the Assistant about abiogenesis.
- Click the Google search provided by the assistant and carry the conversation.
- Ask if there are any images.
- Click the Quick prompts thats show the process or the miller-urey experiment.
Expected result
- The Assistant should provide the information or a link to some images.
Actual result
- Clicking the Quick prompt will have the Assistant stuck in infinite loading.
Please note that Im also getting this Console error:
run_search: Original tab no longer exists, aborting search handoff to avoid interfering with existing conversation Chat.sys.mjs:202:23
fetchWithHistory moz-src:///browser/components/aiwindow/models/Chat.sys.mjs:202
Regression range
N/A
Updated•2 months ago
|
| Reporter | ||
Updated•2 months ago
|
| Reporter | ||
Comment 1•2 months ago
|
||
After further testing this seems to happen every time we continue the conversation from the Homepage into the Sidebar. It is no related to the Quick prompts.
- Type Ps5 games in the Home page smart bar and select Search.
- Open the Sidebar and ask the Assistant about ps5 top 10 games.
The assistant gets stuck in infinite loading.
| Assignee | ||
Comment 2•1 month ago
|
||
console.error: "run_search: Associated window not available or closed, aborting search handoff"
| Assignee | ||
Comment 3•1 month ago
|
||
looks like bug 2012830 did a bad merge conflict resolution changing the context back to win instead of bug 2014802's browsingContext
Comment 4•1 month ago
|
||
:bjohns, since you are the author of the regressor, bug 2012830, could you take a look?
For more information, please visit BugBot documentation.
| Assignee | ||
Comment 5•1 month ago
|
||
looks like bug 2014802 might have introduced some logic issue with checking the browsing context post tool call
| Assignee | ||
Comment 6•1 month ago
|
||
correctly resolve merge conflict between D280868 and D282505 with context object, use pre-tool-call browsing context for post-tool-call checks
Updated•1 month ago
|
Backed out for causing mochitests failures @browser_smartwindow_run_search.js
Comment 10•1 month ago
|
||
Comment 11•1 month ago
|
||
| bugherder | ||
Updated•1 month ago
|
| Reporter | ||
Comment 12•1 month ago
|
||
This issue is verified as fixed in our latest 149 and Nightly 150.0a1 (2026-02-24)
Description
•