Able to reproduce the issue on Mac 10.12.3, Win-10 and Ubuntu 14.04 using chrome reported version #58.0.3029.19 but the same is not reproducible in the latest canary #59.0.3046.0.

Reverse Bisect Information:
=====================
Good build: 59.0.3038.0  Revision(456244)
Bad Build : 59.0.3037.0  Revision(455955)

Change Log URL: 
https://chromium.googlesource.com/chromium/src/+log/a26877dfeb89300f2da958471d2ab9f72766cf38..fead74a8e3d55044bc89fe96500275a0b5e3f24c

From the above change log suspecting below change

Review url: https://codereview.chromium.org/2741783006

brucedawson@ - Could you please check and merge the fix to M-59 if it is a valid candidate.

Thanks...!!

Adding label ReleaseBlock-Stable as it seems to be a recent regression.

Thanks...!!

looks like it's fixed in 58.0.3029.33

Unable to reproduce the issue in Win-10, Mac 10.12.3 and Ubuntu 14.04 using chrome beta version #58.0.3029.54 and latest canary #59.0.3067.0.

Thanks...!!

mirek.kaim@,
As per comment#5,Could you please check the issue & update the thread with your observations on the same.
Thank you!

as i've said in comment 4, it seems to be fixed since 58.0.3029.33 (the issue didn't come back since that version) - that's all i know, sitting on the beta channel.

I'm glad this appears to be fixed. Apologies for not looking at it more closely before.

The blamed change of mine could not be the problem as it makes no difference to the build. One of the changes is just a different way of choosing the 2015/2017 runtime files, and the other one just makes unsupported compilers be an explicit error. The change doesn't change any code that is compiled, or change the toolchain that we use. So, I don't know why the error appeared or why it went away.