Able to reproduce the issue on reported chrome on reported chrome version #71.0.3578.98 using Windows 10 by following steps as per comment#0 " bug2 .gif" file.

When tried testing the issue on chrome version #60.0.3112.113 found a bit different behavior. Observed that after refreshing the page the "foo" variable is not found in the console. When entered the "foo" in console observed same error (foo is not defined) which is seen in reported chrome.

Attached screencast for reference.
@reporter: Could you please review attached screencast and let us know if this can be considered as good or bad behaviour so that it would be really helpful in further triaging of the issue.
Thanks.!

Deleted: 923333.mp4 1.5 MB

	923333.mp4 1.5 MB View Download

Thank you for your reply.

I think the issue was misunderstood. The issue is regarding the eager evaluation feature, which was introduced in Chrome 68, so it could not happen in 60.

The issue isn't that "foo" stops existing (that is expected). It's that the eager evaluated result doesn't update to reflect that foo stopped existing. 

Note how in my gif, you can see the console settings that have "eager evaluation" enabled. Furthermore, note how after the "const foo = 12345", I type "foo" again but I don't press enter. It shows the "12345" as output anyway (i.e. it's eagerly evaluated) which is also expected.

On page refresh, "foo" will stop existing as expected, but the eager evaluated result will still show "12345", which is unexpected. My expectation is that it shouldn't show "12345" as the variable no longer exists. Then you can see that I press enter and get an error, which is expected. The error only shows that "foo" really doesn't exist. 

If I misunderstood your response, please let me know!

Thank you for providing more feedback. Adding the requester to the cc list.

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