Hello,
here the botr tech answer :
We haven't been able to reliably reproduce the issue to determine what asset is actually causing the access denied error that is the root of the issue.
We're going to do a major player release early next month that will significantly change how the player is loaded inside the embed code. It is very well possible that this will clear out this issue too. If not, we will work from there. If at that point the issue still appears we will need a test page where the issue can be reproduced so we can tell what asset is causing the issue, so we can see what needs to be adjusted to fix
I have also some now difficult to reproduce this issue (event with shutting done the browser), so we have to wait now the Q4.
