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

Example URL:
https://github.com/sebakerckhof/chromemjpegproblem

Steps to reproduce the problem:
1. Have an application that servers an MJPEG stream to the browser, in my case it is a nodejs application that serves the images at 1fps. I made a minimal reproduction here: https://github.com/sebakerckhof/chromemjpegproblem

2. Open the mjpeg stream (e.g. using an image tag in an HTML page) in chrome

What is the expected behavior?
Always get to see the latest image that has been sent by the server.

What went wrong?
Chrome always shows the second to last image. Firefox always shows the last image received. When putting the two browsers side-by-side, it is clear that chrome is always one frame behind. This is clearly visible when the mjpeg stream is a slow-updating one, e.g. 1fps or less.

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? N/A 

Does this work in other browsers? Yes 

Chrome version: 52.0.2743.116  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 22.0 r0

This is a follow-up for this issue which shouldn't have been archived by your bot: https://bugs.chromium.org/p/chromium/issues/detail?id=527446