We currently initialize the search component on setInput, that means basically when we attach the controller. That means we initialize the location bar search component when the location bar gets focus, for example. That should not be necessary until the user starts searching. We could probably try to do that lazily from StartSearch by checking mSearches.Length().

Try looks reasonably green: https://treeherder.mozilla.org/#/jobs?repo=try&revision=ef068e63b4329149ea5022efcb9a1009c0d7c827

Comment on attachment 8949102 [details] [diff] [review] Patch Review of attachment 8949102 [details] [diff] [review]: ----------------------------------------------------------------- It looks great. I checked that all the relevant properties are still initialized in a timely manner, I didn't identify any issues with that. Thanks!

Pushed by florian@queze.net: https://hg.mozilla.org/integration/mozilla-inbound/rev/789903045a39 Delay getting the search component service until the first StartSearch, r=mak.