Is this implementation affected by this chrome bug?

First discovered here:
https://stackoverflow.com/questions/47524205/random-high-content-download-time-in-chrome/47684257

Caused by this chrome feature:
https://www.chromestatus.com/feature/5745543795965952

More detail:
https://github.com/TryGhost/Ghost/issues/7934