Closed Bug 1542662 Opened 5 years ago Closed 2 years ago

4K video flickers black once per second or so using WebRender on FireStick 4K

Categories

(Core :: Graphics: WebRender, defect, P3)

ARM
Android
defect

Tracking

()

RESOLVED INCOMPLETE
Tracking Status
firefox66 --- wontfix
firefox67 --- fix-optional
firefox68 --- affected

People

(Reporter: cpearce, Unassigned)

Details

(Whiteboard: [gvtv:p2])

While playing 4K video on the Amazon FireStick 4K with GeckoViewExample, approximately once per second I see what looks like a video frame painted as black.

I'm building GVE locally. This seems to be a recent regression; I updated by my mozilla-central source tree, and my FireOS (to 6.2.6.3(NS6263/2349)) on Friday, and this started happening.

Screencast:
https://youtu.be/mDCf-JjCnhc

Whiteboard: [gvtv] → [gvtv:p1]

Is this something we can find a regression range for?

Flags: needinfo?(cpearce)
Priority: -- → P1

I realised I had preffed on WebRender for testing and forgotten to turn it off. Once I disable WebRender, the flickering stops. So I guess this is a problem with WebRender, or the interaction of the media stack with WebRender.

cpeterson: I assume that we're not planning on using WebRender in the FireStick/GV MVP, and so this doesn't need to be [gvtv:p1]?

Component: Audio/Video: Playback → Graphics: WebRender
Flags: needinfo?(cpearce) → needinfo?(cpeterson)

(In reply to Chris Pearce [:cpearce (GMT+13)] from comment #2)

cpeterson: I assume that we're not planning on using WebRender in the FireStick/GV MVP, and so this doesn't need to be [gvtv:p1]?

That's correct. WebRender is not a priority for FFTV at this time.

Flags: needinfo?(cpeterson)
Summary: 4K video flickers black once per second or so on FireStick 4K → 4K video flickers black once per second or so using WebRender on FireStick 4K
Whiteboard: [gvtv:p1] → [gvtv:p2]

Dropping the priority so graphics can re-triage as appropriate.

Priority: P1 → --
Priority: -- → P3
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.