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.

Merging to M52

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
Review-Url: https://codereview.chromium.org/2040093002
Cr-Commit-Position: refs/heads/master@{#398226}
(cherry picked from commit 5795198277f6c7e1e5871d343c1dbadba1a505d6)

Committed: https://chromium.googlesource.com/chromium/src/+/1f9b16ef7e1d1ad069331705a08eaf59cea7897a

[ananta, 2016-06-22 22:24:39]

Description was changed from

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

Merging to M52

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

Review-Url: https://codereview.chromium.org/2040093002
Cr-Commit-Position: refs/heads/master@{#398226}
(cherry picked from commit 5795198277f6c7e1e5871d343c1dbadba1a505d6)
==========

to

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

Merging to M52

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

Review-Url: https://codereview.chromium.org/2040093002
Cr-Commit-Position: refs/heads/master@{#398226}
(cherry picked from commit 5795198277f6c7e1e5871d343c1dbadba1a505d6)

Committed:
https://chromium.googlesource.com/chromium/src/+/1f9b16ef7e1d1ad069331705a08e...
==========

[ananta, 2016-06-22 22:24:41]

Committed patchset #1 (id:1) manually as
1f9b16ef7e1d1ad069331705a08eaf59cea7897a.