Search start-up service intialization browser console error
Categories
(Firefox :: Address Bar, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox-esr78 | --- | unaffected |
firefox80 | --- | unaffected |
firefox81 | --- | unaffected |
firefox82 | --- | disabled |
firefox83 | --- | verified |
People
(Reporter: aflorinescu, Assigned: bugzilla)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
[Sugested Severity:]
S4 until investigated
[Description:]
First startup + fast type @ in the address bar
[Environment:]
Ubuntu 20.04 / Windows 10
82.0a1 2020-09-15
[Steps:]
- Create a new profile.
- At fist start-up fast type @ in the addressbar.
[Actual Result:]
Error: Something tried to use the search service before it's been properly intialized. Please examine the stack trace to figure out what and where to fix it:
_ensureinitialized@resource://gre/modules/searchservice.jsm:233:15
getenginebyname@resource://gre/modules/searchservice.jsm:1408:10
setsearchmode@resource:///modules/urlbarinput.jsm:1270:34
seturi@resource:///modules/urlbarinput.jsm:364:12
onlocationchange@chrome://browser/content/browser.js:5289:15
calllisteners@chrome://browser/content/tabbrowser.js:832:31
_callprogresslisteners@chrome://browser/content/tabbrowser.js:846:22
_callprogresslisteners@chrome://browser/content/tabbrowser.js:5826:46
onlocationchange@chrome://browser/content/tabbrowser.js:6239:14
SearchService.jsm:233:15
[Note:]
- It's a bit intermittent, so a slow PC would help.
- This might also be a search shortcuts (bug 1644572) related issue, but blocking post-modernization first for investigation.
Comment 1•4 years ago
|
||
This is the address bar (search shortcuts) trying to access the search service too early and not checking if it is initialised first:
Assignee | ||
Updated•4 years ago
|
Updated•4 years ago
|
Assignee | ||
Comment 2•4 years ago
|
||
Comment 4•4 years ago
|
||
bugherder |
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Reporter | ||
Comment 5•4 years ago
|
||
Verified that the search initialization issue is solved on Win10 - 82.0b7. However, given that the search shortcuts is now disabled on 82, this is not entirely relevant, so moving the flags to keep this bug tracked for further verification on 83.
Comment 6•4 years ago
|
||
I have managed to reproduce the issue using Fx82.0a1 on Ubuntu and Windows as mentioned in the bug.
Verified the issue using the latest Fx83.0a1 on Windows 10 and Ubuntu 18.04. The eror is no longer when '@' is typed as soon as Firefox starts.
Updated•4 years ago
|
Description
•