Closed Bug 1432245 Opened 7 years ago Closed 5 years ago

HLS Video Freezes after first chunk is rendered with Hardware acceleration enabled on Win 10


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

57 Branch





(Reporter: virga, Unassigned)


(Blocks 1 open bug)


User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0
Build ID: 20180103231032

Steps to reproduce:

Play video with HLS Javascript type player on Win 10 with current Firefox 57 AND Options > "Use hardware acceleration when available" is checked or Options > "Use recommend performance settings" is checked. 
Using the following Stream URLs and players

Stream URL:

It also happens with a single delivery rate:

Players that show the problem:

Demo Versions - paste in the URL above:

The same URLs in other browsers play fine. 

Actual results:

Video freezes at the end of the first chunk (10s) - audio continues.

HLS video delivered video from Wowza Server, the first video chunk loads and renders then the video freezes at the end of the first chunk (10s) the audio continues and an occasional key frame updates. 

This does not happen in other browsers or device playback. It does not happen if the two performance options are unchecked. 

It DOES happen no matter what content process settings are used. 

This was tested on multiple Windows 10 systems with same results. 
This problem DID NOT happen on macOS.    

Expected results:

The Video should continue to play.
Component: Untriaged → Audio/Video: Playback
Product: Firefox → Core
Thanks for the report. It sounds like this is related to our use of hardware acceleration. Could you please attach the graphics section from the about:support page in your browser on the machine which is showing the problem.
Assignee: nobody → dglastonbury
Flags: needinfo?(virga)
Priority: -- → P2
Assignee: dglastonbury → giles
Assignee: giles → nobody

No response from reporter - closing as incomplete.

Closed: 5 years ago
Resolution: --- → INCOMPLETE
Flags: needinfo?(virga)
You need to log in before you can comment on or make changes to this bug.