BISECT: 366717 (known good) - 366726 (first known bad) which is inside 49.0.2600.0-49.0.2601.0 range.
https://chromium.googlesource.com/chromium/src/+log/02cefdcaff9d73c0f72033ee9d2d79e7f0cf8383..c2e05cef29f33b331cbc33f742246a012e184abe?pretty=fuller
Suspecting https://codereview.chromium.org/1536213002

The bug still exists but doesn't occur with the new work-in-progress MD history.

+Devlin to please help with routing.

Unable to reproduce this issue, we tested this issue on windows10, Mac 10.12 and ubuntu 14.04 machines with chrome version stable 53.0.2785.116.

Observed that refreshing history tab doesn't have any effect on NTP(with blank extension).

Check the attached screencast

Could you please try this scenario with clean profile without using any apps or extensions in your browser and let us know your observation.

Deleted: Issue-651873.mp4 2.1 MB

	Issue-651873.mp4 2.1 MB View Download

Try loading the unpacked extension from the link mentioned.

Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" for another review and adding "Needs-Review" label for tracking.

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

I just tried this with loading the unpacked blank ntp extension and md history, and everything seems to be working fine.  Are you still seeing this on the latest versions of chrome?

Able to reproduce the issue in windows 10 with chrome version #53.0.2785.116 with the provided link in comment #0.

But unable to reproduce the issue on latest stable version #55.0.2883.87

 pdknsk@ could you please update your browser to latest version to retest the scenario and let us know your observations. 

I can still reproduce on 56.0.2924.28 using the old history. I don't use md-history. In a way, this makes the bug obsolete, as it's now hidden. You decide.

Some clarification. This occurs with many chrome:// pages, like chrome://settings, which has not been switched to MD yet, and probably won't be for some time. It doesn't occur with chrome://downloads (MD). So this bugs gets auto-fixed (or hidden rather) when all of chrome:// is switched to MD.

Some pages do not produce the bug, like chrome://flags or chrome://gpu.

Able to reproduce this issue on Windows 10, Ubuntu 14.04  with chrome version 55.0.2883.87 and Mac 10.12.2 on chrome stable version 55.0.2883.95 and also in current canary version #57.0.2971.0
Issue is broken in M49.

Bisect Info:
===========
Good build : 49.0.2600.0,  Revision Range -366701
Bad build  : 49.0.2601.0,  Revision Range -366761

After executing the bisect(old) script , i got the following CL's between good and bad build versions
===========================================
https://chromium.googlesource.com/chromium/src/+log/7623e624861d45f61632aaba650b4182c5d022ff..6d4faa11235e13e35c202ec5411360cffbb81111

The suspecting Change Log is :
-----------
https://chromium.googlesource.com/chromium/src/+/6c57ed900648bf699491cb8d2bb90f82f703ec20

From the above CL suspecting the below change
---------------------------
https://codereview.chromium.org/1536213002

limasdf@- Could you please look into this issue, if it's related to your change?  if not could you please help us to reassign this issue to the right owner.

Hi kkaluri,
I think my change(https://codereview.chromium.org/1536213002) is not culprit. because my change has effect only in chrome://extensions.

But I'll take a look more deeply.

You started fixing this bug over two years ago. Are you still working on it? You can update the status to "archived", "wontfix", or "closed". You can remove yourself as owner and change status to "untriaged", but if this is still a real bug, please do not sit on it.