providing Predator results,
The result is a list of CLs that change the crashed files. 

Author: alexclarke
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/cdf5b1fbdbfed58d0a0450597d3666c5a2159c30
Time: Tue Jan 24 19:11:06 2017
File task_queue_manager.cc is changed in this cl (and is part of stack frame #5, "blink::scheduler::TaskQueueManager::MaybeRecordTaskDelayHistograms"; frame #6, "blink::scheduler::TaskQueueManager::ProcessTaskFromWorkQueue"; frame #7, "blink::scheduler::TaskQueueManager::DoWork")
Minimum distance from crash line to modified line: 2. (file: task_queue_manager.cc, crashed on: 320, modified: 322).

assigning to alexclarke@, could you please check the issue and help.

https://codereview.chromium.org/2653643002 shouldn't change anything w.r.t the histogram.

Looking at the regression range, I'm wondering if https://codereview.chromium.org/2655673002 might be related?

I'd guess it's the enable-by-default.  That's not in the regression range but perhaps this one got delayed by the g_allocator find.

Being enabled means that TSAN is doing all its test cases with persistent histograms enabled and is thus finding these new races.  Going to be a busy week, I suspect...

Looks like accesses to g_allocator.  The fix for that went in 16 hours ago and the report shows the last git commit being 18 hours ago.