Fixed track id remapping in MSE FrameProcessor

Fixed track id remapping in MSE FrameProcessor

Previously FrameProcessor couldn't handle cases where audio and video
track ids were swapped between the previous and current init segment,
because we tried to do an in-place update, which is impossible to do
correctly when track ids have been swapped. Consider the case where
in the first init segment A=1,V=2 and in the second segment A=2,V=1.
In such case we can't simply move let's say track A from 1 to 2,
because track id 2 is occupied by V, and vice versa.
This CL implements a more advanced logic, that will record how track
ids have changed between segments and will then update all track buffer
mappings in FrameProcessor::UpdateTrackIds at once.

BUG=660247
Committed: https://crrev.com/b9233a906062fd461503fca84fa2223ee315bfaf
Cr-Commit-Position: refs/heads/master@{#428473}

[servolk, 2016-10-28 03:18:29]

The CQ bit was checked by servolk@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-10-28 03:18:51]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[servolk, 2016-10-28 03:23:43]

Description was changed from

==========
Fixed track id remapping in MSE FrameProcessor

Previously FrameProcessor couldn't handle cases where audio and video
track ids were swapped between the previous and current init segment,
because we tried to do an in-place update. Instead of performing single
track update we need to record how the id of each track has changes and
then perform updates for all tracks/ids at once.

BUG=660247
==========

to

==========
Fixed track id remapping in MSE FrameProcessor

Previously FrameProcessor couldn't handle cases where audio and video
track ids were swapped between the previous and current init segment,
because we tried to do an in-place update, which is impossible to do
correctly when track ids have been swapped. Consider the case where
in the first init segment A=1,V=2 and in the second segment A=2,V=1.
In such case we can't simply move let's say track A from 1 to 2,
because track id 2 is occupied by V, and vice versa.
This CL implements a more advanced logic, that will record how track
ids have changed between segments and will then update all track buffer
mappings in FrameProcessor::UpdateTrackIds at once.

BUG=660247
==========

[servolk, 2016-10-28 03:24:17]

servolk@chromium.org changed reviewers:
+ chcunningham@chromium.org, wolenetz@chromium.org

[commit-bot: I haz the power, 2016-10-28 04:33:46]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-10-28 04:33:46]

Dry run: Try jobs failed on following builders:
  android_n5x_swarming_rel on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/android_n5x_...)

[cblume, 2016-10-28 05:41:19]

Thank you for fixing this so quickly and staying late.

[servolk, 2016-10-28 16:11:18]

The CQ bit was checked by servolk@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-10-28 16:11:33]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-10-28 16:44:39]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-10-28 16:44:40]

Dry run: This issue passed the CQ dry run.

[servolk, 2016-10-28 18:34:06]

On 2016/10/28 05:41:19, cblume wrote:
> Thank you for fixing this so quickly and staying late.

Matt/Chris, PTAL. Let's have get this fix into master ASAP, so that it gets
tested and gives us reassurance that it's safe to cherry-pick into M55.

[chcunningham, 2016-10-28 19:40:09]

Nice change. LGTM

[servolk, 2016-10-28 20:14:29]

The CQ bit was checked by servolk@chromium.org

[commit-bot: I haz the power, 2016-10-28 20:15:12]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-10-28 20:20:57]

Description was changed from

==========
Fixed track id remapping in MSE FrameProcessor

Previously FrameProcessor couldn't handle cases where audio and video
track ids were swapped between the previous and current init segment,
because we tried to do an in-place update, which is impossible to do
correctly when track ids have been swapped. Consider the case where
in the first init segment A=1,V=2 and in the second segment A=2,V=1.
In such case we can't simply move let's say track A from 1 to 2,
because track id 2 is occupied by V, and vice versa.
This CL implements a more advanced logic, that will record how track
ids have changed between segments and will then update all track buffer
mappings in FrameProcessor::UpdateTrackIds at once.

BUG=660247
==========

to

==========
Fixed track id remapping in MSE FrameProcessor

Previously FrameProcessor couldn't handle cases where audio and video
track ids were swapped between the previous and current init segment,
because we tried to do an in-place update, which is impossible to do
correctly when track ids have been swapped. Consider the case where
in the first init segment A=1,V=2 and in the second segment A=2,V=1.
In such case we can't simply move let's say track A from 1 to 2,
because track id 2 is occupied by V, and vice versa.
This CL implements a more advanced logic, that will record how track
ids have changed between segments and will then update all track buffer
mappings in FrameProcessor::UpdateTrackIds at once.

BUG=660247
==========

[commit-bot: I haz the power, 2016-10-28 20:20:58]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-10-28 20:24:19]

Description was changed from

==========
Fixed track id remapping in MSE FrameProcessor

Previously FrameProcessor couldn't handle cases where audio and video
track ids were swapped between the previous and current init segment,
because we tried to do an in-place update, which is impossible to do
correctly when track ids have been swapped. Consider the case where
in the first init segment A=1,V=2 and in the second segment A=2,V=1.
In such case we can't simply move let's say track A from 1 to 2,
because track id 2 is occupied by V, and vice versa.
This CL implements a more advanced logic, that will record how track
ids have changed between segments and will then update all track buffer
mappings in FrameProcessor::UpdateTrackIds at once.

BUG=660247
==========

to

==========
Fixed track id remapping in MSE FrameProcessor

Previously FrameProcessor couldn't handle cases where audio and video
track ids were swapped between the previous and current init segment,
because we tried to do an in-place update, which is impossible to do
correctly when track ids have been swapped. Consider the case where
in the first init segment A=1,V=2 and in the second segment A=2,V=1.
In such case we can't simply move let's say track A from 1 to 2,
because track id 2 is occupied by V, and vice versa.
This CL implements a more advanced logic, that will record how track
ids have changed between segments and will then update all track buffer
mappings in FrameProcessor::UpdateTrackIds at once.

BUG=660247

Committed: https://crrev.com/b9233a906062fd461503fca84fa2223ee315bfaf
Cr-Commit-Position: refs/heads/master@{#428473}
==========

[commit-bot: I haz the power, 2016-10-28 20:24:20]

Patchset 1 (id:??) landed as
https://crrev.com/b9233a906062fd461503fca84fa2223ee315bfaf
Cr-Commit-Position: refs/heads/master@{#428473}

[wolenetz, 2016-10-28 23:29:29]

LGTM