Fix CastSession/FlingingRenderer creation race
The FlingingRenderer needs a MediaController in order to be created. RemotingMediaRouteProvider signals MediaRoute creation as soon as we start to launch the RemotingCastSession. This can trigger the creation of a FlingingRenderer before the CastSession finishes launching, which means that FlingingRenderer ends up with a null MediaController. This CL delays the moment at which RemotingMediaRouteProvider completes the route creation request, to after the RemotingCastSession launches. This guarantees that we won't create a FlingingRenderer until we have a valid MediaController to retrieve. Bug: 790766 Change-Id: Ib74ab54890976f7735140e7eac79548898fbb667 Reviewed-on: https://chromium-review.googlesource.com/1043527 Commit-Queue: Thomas Guilbert <tguilbert@chromium.org> Reviewed-by:Derek Cheng <imcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#557258}
Showing
Please register or sign in to comment