While testing this problem was found. This issue is not occurring on other browsers and Pre version Chrome 56. I discovered the flaw/issue, then our developer above could not replicate the issue. It was found that after upgrading the Chrome to the same version this issue was also then presenting. So this is certainly a isolated Brower + Version bug for dynamic image loading. 

Also at times the images initially load then 0.5-1s later then show broken images, however the URL direct to the image still shows the image file as a working url.

Here is a video that demonstrates the issue. Between 25-35 seconds you can see the load then break.
https://www.screencast.com/t/l4i8rXBBoiHP

I can repro this in M57 on Windows 10, but not Linux.

The console is full of messages about image thumbnails loading. Could you please explain to us how the images are served? Is it possible that you are seeing a low-res thumbnail and then the high-res version is simply not loading, resulting the broken image?

Is it always the same images failing? I know that the ones I saw failing were the same as those failing in the screencast.

I dug some more. A DevTools network trace shows that the broken images are cancelled requests. There are any number of reasons for that but the fact it's Windows only suggests something in the network stack rather then the image code.

A brief poke on Stack Exchange suggests that cancelled requests typically mean race conditions where something happens to make Chrome think the resource cannot be processed.

Raising priority as it sounds like an M56 regression.

Still waiting on feedback requested in Comment #3. I think we should de-prioritize until we get feedback.

And bisect?

Wasn't able to reproduce (Chrome 57 windows).
Given the lack of additional details, let's close for now.
Please reopen a new issue with more details if this still is happening.