Fix black frames on segment boundaries in H/W decoded h.264 video on windows.

Fix black frames on segment boundaries in H/W decoded h.264 video on windows.

When we detect a segment boundary we reinitialize the decoder. Currently
on Windows that results in tearing down the decoder instance the
D3D9/D3D11 device objects, the output picture buffers etc.

We don't need to tear down the output picture buffers and the d3d device
objects. This fixes the black frame which shows up due to the picture
buffers getting destroyed and new ones getting created.

In any case if the resolution changes we do request new output buffers
anyways.

I tested the test case in bug 594266 which was the reason for the config
change code in the first place. That still works in D3d9 and D3D11.

BUG=616349
Committed: https://crrev.com/5795198277f6c7e1e5871d343c1dbadba1a505d6
Cr-Commit-Position: refs/heads/master@{#398226}

[ananta, 2016-06-07 00:36:15]

ananta@chromium.org changed reviewers:
+ sandersd@chromium.org

[sandersd (OOO until July 31), 2016-06-07 01:11:39]

lgtm

[ananta, 2016-06-07 01:36:40]

The CQ bit was checked by ananta@chromium.org

[commit-bot: I haz the power, 2016-06-07 01:37:09]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/2040093002/1

[commit-bot: I haz the power, 2016-06-07 04:40:23]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-06-07 04:42:00]

Description was changed from

==========
Fix black frames on segment boundaries in H/W decoded h.264 video on windows.

When we detect a segment boundary we reinitialize the decoder. Currently
on Windows that results in tearing down the decoder instance the
D3D9/D3D11 device objects, the output picture buffers etc.

We don't need to tear down the output picture buffers and the d3d device
objects. This fixes the black frame which shows up due to the picture
buffers getting destroyed and new ones getting created.

In any case if the resolution changes we do request new output buffers
anyways.

I tested the test case in bug 594266 which was the reason for the config
change code in the first place. That still works in D3d9 and D3D11.

BUG=616349
==========

to

==========
Fix black frames on segment boundaries in H/W decoded h.264 video on windows.

When we detect a segment boundary we reinitialize the decoder. Currently
on Windows that results in tearing down the decoder instance the
D3D9/D3D11 device objects, the output picture buffers etc.

We don't need to tear down the output picture buffers and the d3d device
objects. This fixes the black frame which shows up due to the picture
buffers getting destroyed and new ones getting created.

In any case if the resolution changes we do request new output buffers
anyways.

I tested the test case in bug 594266 which was the reason for the config
change code in the first place. That still works in D3d9 and D3D11.

BUG=616349

Committed: https://crrev.com/5795198277f6c7e1e5871d343c1dbadba1a505d6
Cr-Commit-Position: refs/heads/master@{#398226}
==========

[commit-bot: I haz the power, 2016-06-07 04:42:01]

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