Narrow bisect:
https://chromium.googlesource.com/chromium/src/+log/9349e8fc1900cab593c7b3c17bc8d840fcae6f8d..689d5629cf7d5d23897fb99b847eaa0999289867?pretty=fuller&n=30

Suspecting: 438205 ?

Could someone from In-house team run a per-revision bisect?

Executed old bisect script instead of per-revision bisect due to below error.

The URL "chrome://ntp-tiles-internals/" which was provide in the issue was showing the error, "This site can’t be reached", so had to execute old bisect tool.
Please let me know if any more information is required.
Note: Removing Needs Bisect label as of now.
Thank You. 

Thank you Ravi for the update. For me, old script is also giving the same error (technically both scripts are same) and not sure how it's worked for you guys, just wanted to know.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/d6336797781587abf6c3fa648d034315714d1134

commit d6336797781587abf6c3fa648d034315714d1134
Author: sfiera <sfiera@chromium.org>
Date: Mon Feb 27 15:44:08 2017

chrome://ntp-tiles-internals: hide when incognito

Previously I just disabled the callbacks. In addition to that, send back
an empty configuration and site list, to make the page properly display
that everything is disabled and there are no sites in incognito.

Without this change, the "View JSON" button appears for popular sites,
but causes a crash because there's no PopularSites object.

BUG= 682622 , 696471 ,681774

Review-Url: https://codereview.chromium.org/2721603002
Cr-Commit-Position: refs/heads/master@{#453220}

[modify] https://crrev.com/d6336797781587abf6c3fa648d034315714d1134/components/ntp_tiles/webui/ntp_tiles_internals_message_handler.cc
[modify] https://crrev.com/d6336797781587abf6c3fa648d034315714d1134/components/ntp_tiles/webui/resources/ntp_tiles_internals.js

(not working on client-side Chrome any more)