Tested the issue on 60.0.3112.113 using Windows 7 with steps mentioned below and is not reproducible

Visited amazon.com, naver.com multiple times ,closed those tabs and observed thumbnails of most visited sites in NTP.

@Reporter:Could you please re-check the same on fresh profile and provide screenshot for reference.

It's not quite clear to me what the bug is here. It's fine for TopSites to show a site you've only visited once, if you haven't visited anything else recently. OTOH, in a profile with a lot of history, it's expected that the list is quite stable.
Could you provide some more detail on what exactly is happening, and what you would expect to see instead?

Some background: TopSites in fact also uses a "frecency" algorithm. It's typically updated when you open a new tab, and also periodically in the background.

@1: Tried it and still unable to figure out what cause it.

@2: I'm visiting all eight sites nearly every day which is why it's weird.

TopSites uses a similar algorithm to frecency, I was told. Think a dev called it 'recency'.

Anyway, wrong or not I've used Firefox a lot and written a frecency algorithm in javascript in an extension for Chrome (as much as a could with the limited and buggy api). Frecency algorithm in my experience just don't behave like what I've observed. Although I did use the values ("algorithm settings") that Firefox use. Perhaps chrome uses different values yet it still behaves weirdly.

I'd like to check the underlying database values to see what's happening. Hence the request for a diagnostic debug panel of sorts. I have checked the TopSites sql file however I only saw the results and not the raw data it use.

Perhaps a history diagnostic panel that have a topsites tab since history needs one too?

Can the history data be corrupt in some way? Is there a way to check if it is?

Thank you for providing more feedback. Adding requester "sc00335628@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I made a search on google and Chrome crashed. As expected when starting it up again the bug showed its ugly head, this time. Perhaps this screenshot helps.

Deleted: topsites__db_sql_screenshot_send.png 108 KB

	topsites__db_sql_screenshot_send.png 108 KB View Download

Hm, the highlighted row has rank 10, so it shouldn't actually show up on the NTP. Though if it was only visited once, it's still weird that it is so high.

If you're interested, the actual TopSites algorithm is implemented in VisitSegmentDatabase::QuerySegmentUsage, here: https://cs.chromium.org/chromium/src/components/history/core/browser/visitsegment_database.cc?type=cs&sq=package:chromium&l=205

@Reporter: Are you still seeing this issue on latest channels, please check the above comment and respond the comment with latest behavior. You can download latest build from https://www.chromium.org/getting-involved/dev-channel.

Due to lack of user feedback closing this issue.
Please feel free to raise a new one if you face any chrome issue further.
Thanks..!

I think that item is showing up because the domain is google.se. Most of them, if not all of them, are google searches. Perhaps this single visit is showing up because google.se is often visited to search for things?