No, I can't reproduce the problem here. But from the source code, I can see a scenario where a CODEC bug indeed leads to this problem. It happens when the CODEC erroneously triggers an event that marks the video as finished.

I can't fix this CODEC of course, but I've added a diagnostics output to the engine so that you can see if this is the reason.