UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36

Steps to reproduce the problem:
1. Create table using d3 javascript library. 
2. Create API call in WebAPI to return collection of serialized (JSON) objects to render in d3 table.
3. Access page on which the table exists, initiating a call to the WebAPI and attempt to populate table.

What is the expected behavior?
The expected behavior, with less than 1,500 records for the table, is a render time of less than 2 seconds to completely load the DOM. In IE11 and Firefox, render time meets those specs - approx 1.6 seconds. Using previous version of Chrome, load times are approx 1.6 seconds. 

What went wrong?
Load times for same page are now in excess of 6 seconds to completely load the DOM. Nothing has changed in any of the related code base, physical architecture, network, etc. Only difference is the latest Chrome update being applied. I have ruled out all other factors, and verified on an older version of Chrome that the behavior was not present before latest update.

Did this work before? Yes Whichever version came before the one pushed out this last week.

Chrome version: 61.0.3163.100  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

I would really like to see this fixed soon. I'm certain other companies that use d3 must have similar issues. I HATE having to recommend to my users to use IE - ugh! Not sure what happened, but seems like something with the parsing/serializing/deserializing of JSON on ajax requests has changed for the worse.