Hey Alain,
If you look at the code above, we basically already do that in our workaround (which resolves the issue)? Unless I’m misunderstanding the location you’re indicating? That workaround (using the same acquisition order) is _a_ fix for this issue, but you wouldn’t expect everyone to do this before they call Tick on the slate application? This is an internal implementation detail.
(what I don’t know is why the movie player is getting this lock earlier, and/or doesn’t release it before calling tick)