Bugzilla

Since history appears in the menu, it looks like it is being stored, so this is some kind of selection bug in the Address Bar.
History is stored also based on counts extracted from the database.

In comment 0 I see you say it's when "clicking" the address bar, so I wonder if you're seeing the bug only in that case, or also when actually typing a few characters. Like if you type "am" or similar short strings, do you see history results then?
I think

Since history appears in the menu, it looks like it is being stored, so this is some kind of selection bug in the Address Bar.
History is stored also based on counts extracted from the database.

In comment 0 I see you say it's when "clicking" the address bar, so I wonder if you're seeing the bug only in that case, or also when actually typing a few characters. Like if you type "am" or similar short strings, do you see history results then?

I think what happens here is that with the introduction of Trending Searches/Recent Searches there is always a provider with high priority running, that means the basic Places provider doesn't run because it has a lower priority. Before the change the TopSites provider was not running thus we were moving to lower priorities providers and Places was running a zero prefix search, and thus showing history.
Dale, do you think this is a valid theory?