Chrome Version: 62.0.3166.0
OS: Windows

What steps will reproduce the problem?
(1) Use Chrome Canary for a while.

What is the expected result?

Expect that the browser remains responsive.

What happens instead?

The browser eventually hangs, permanently.

Overnight it hung in FindHistogram, trying to take a lock. (Running Canary w/out heap profiling).

Yesterday I had it hang twice while in-use, and the hangs looked like they were in memory allocations in the statistics code.  (These were when running *with* heap profiling enabled)