As my colleague Tsvetina mentioned the problem lies in the Google API. I have researched for possible solution but most of these suggest passing additional parameters when initializing the YouTube player. However our code currently does not expose a way to pass the parameters. That said the only way is to override one of our internal methods which is not recommended. Moreover it is not 100 sure that adding these parameters will resolve the matter as some of the times I was not able to reproduce the error when loading the video.
Since the problem lies in the Google API actually fallback I am not sure that you will experience problems such as stopping the video or preventing it from playing. If however such occur we will provide the necessary override for the part which initializes the player.