Friday's Nightly update broke the address bar and New Tab page functions for me.

Address bar does not show history or search suggestions. It's unresponsive to typing a keyword and pressing Enter. It's also unresponsive to entering www.mozilla.org and pressing Enter. Entering the full URL such as https://www.mozilla.org and pressing Enter works.

Top Sites and Highlights on the New Tab page are also blank. I can't enter any text to the search bar on the New Tab page.

I tried creating a new profile and restarting in safe mode but the problems persist.

This issue can be related to bug #1544214. Could you confirm this please?

(In reply to Virtual_ManPL [:Virtual] - (please needinfo? me - so I will see your comment/reply/question/etc.) from comment #1)

This issue can be related to bug #1544214. Could you confirm this please?

Probably related, since I'm using the tr locale.

I'll wait for the next update to see if it's fixed.

This issue has been fixed for a few days now.

Thanks for reporting back

Latest Nightly update brought this issue back.

I've just tried this with the latest tr on Mac (build id: 20190425220817) and I can't reproduce.

Please could you check the browser console and see if there's any error messages being reported there on startup?

If there isn't please could you set the browser.search.log preference to true, restart Firefox, and then look at the console again. It'd be useful if we could see that output to know if there's some sort of issue with the search engines.

Something weird happened:
I had a pinned Gmail tab and thinking that it might affect the browser console output, I wanted to close it first. However, the issue disappeared after closing the pinned tab and restarting the browser. Now I can't reproduce it and I have no idea if the pinned tab had anything to do with it or not.

The priority flag is not set for this bug.
:adw, could you have a look please?

For more information, please visit auto_nag documentation.

Selim, please let us know if it happens again, noting comment 6. I'm not sure how it could be related to a pinned tab, but who knows.

I'll give this a P3 for now, but if anyone disagrees please change. It looks like a big problem when it occurs, but without more info it's hard to investigate.

This is still non actionable, we need better steps to reproduce the problem, to be able to do something about it :(