1231905 - Youtube HD videos using HTML5/h264 are not hardware decoded

Status: RESOLVED DUPLICATE of bug 1257013

(Core :: Audio/Video: Playback, defect, P2)

Description

[Karthikeyan Sivaraj]

Attachment: about_support_graphics_after.png

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0
Build ID: 20151029151421

Steps to reproduce:

System: Windows 10 Pro 64-bit. Core i5-5250U with integrated GPU (HD Graphics 6000).
Play any youtube 4K video with HTML5/h264. eg: https://www.youtube.com/watch?v=0NTOZbjg6SE



Actual results:

Video playback starts ok, but then becomes choppy after a couple of seconds. CPU usage then stays around 90-100%. The about:support page has the following errors indicating hardware decoding has been disabled:
DXVA disabled errors:
(#0) Error	[D2D1.1] 4CreateBitmap failure Size(17160,30) Code: 0x80070057 format 0
(#1) Error	Too many dropped/corrupted frames, disabling DXVA


Expected results:

h264 video should be hardware decoded with smooth playback. By comparison, using the Microsoft Edge browser, the playback was smooth and CPU usage was 5-15%.

Comment 1

[Karthikeyan Sivaraj]

Attachment: about_support_graphics_before.png

abou:support page when FF is started

Comment 2

[Karthikeyan Sivaraj]

Attachment: FF_cpu_usage.png

Comment 3

[Karthikeyan Sivaraj]

Attachment: Edge_cpu_usage.png

Comment 4

[Karthikeyan Sivaraj]

Attachment: about_support_full.txt

Comment 5

[Karthikeyan Sivaraj]

Further details:
* Tried again after updating to the latest graphics driver from Intel, but still see issue.
* The problem is also seen in the latest Firefox nightly(45.0a1) with a new profile

Comment 6

[Ralph Giles (:rillian)]

I would have expected the intel gpu to work.

Comment 7

[Anthony Jones (:ajones, :kentuckyfriedtakahe, :k17e)]

We tweaked the numbers since 42. Does it still happen in nightly?

Comment 8

[Karthikeyan Sivaraj]

I no longer have access to the system the issue was seen in. Hence, I can't confirm with the latest nightly. However, I did see the issue in 45.0a1 nightly when I tested it. Hope that helps.