1586130 - Switching to full screen videos on FireFox produces a blank screen

Status: REOPENED

(Core :: Graphics, defect, P2)

Description

[Anish]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:69.0) Gecko/20100101 Firefox/69.0

Steps to reproduce:

Stream a video on any platform; mostly Netflix or YouTube.
Clicked on full screen option to go to full screen mode

Actual results:

After switching to FS, the audio kept playing but nothing was showing on the screen, window was a blank screen with sound.
Switched back to smaller window and video came back.

Expected results:

Video and audio both should have been present in the full screen option

Comment 1

[Anish]

Also, transition time between switching from mini windows to full screen and vice versa is quite long; up to 3 seconds

Comment 2

[C.M.Chang[:chunmin]]

I cannot reproduce it on my Windows with Firefox 69(stable) and 71(Nightly). If you can watch video normally, it sounds like the decoder works fine.
Is this reproducible in Firefox Nightly (https://www.mozilla.org/en-US/firefox/channel/desktop/#nightly) ?

Comment 3

[Anish]

(In reply to C.M.Chang[:chunmin] from comment #2)

I cannot reproduce it on my Windows with Firefox 69(stable) and 71(Nightly). If you can watch video normally, it sounds like the decoder works fine.
Is this reproducible in Firefox Nightly (https://www.mozilla.org/en-US/firefox/channel/desktop/#nightly) ?

I haven't tried with Nightly however the issue mainly pops up with Netflix. And this only happens with Firefox, chrome or edge doesn't have the issue.

Comment 4

[C.M.Chang[:chunmin]]

Can you go to about:config (you will need to click accept the risk), search media.gpu-process-decoder on the search bar, then set media.gpu-process-decoder to false and see if you can reproduce the problem?

Comment 5

[Anish]

(In reply to C.M.Chang[:chunmin] from comment #4)

Can you go to about:config (you will need to click accept the risk), search media.gpu-process-decoder on the search bar, then set media.gpu-process-decoder to false and see if you can reproduce the problem?

Yeap, this definitely seemed to do the trick. No more hanging or blank screens for now and transition time also down.

I'll observe for a few hours and get back to you it doesn't pan out. Thanks.

Comment 6

[C.M.Chang[:chunmin]]

(In reply to anishreddy20.ar from comment #5)

(In reply to C.M.Chang[:chunmin] from comment #4)

Can you go to about:config (you will need to click accept the risk), search media.gpu-process-decoder on the search bar, then set media.gpu-process-decoder to false and see if you can reproduce the problem?

Yeap, this definitely seemed to do the trick. No more hanging or blank screens for now and transition time also down.

Michael, would you mind having a look?

Comment 7

[Michael Froman [:mjf]]

(In reply to C.M.Chang[:chunmin] from comment #6)

(In reply to anishreddy20.ar from comment #5)

(In reply to C.M.Chang[:chunmin] from comment #4)

Can you go to about:config (you will need to click accept the risk), search media.gpu-process-decoder on the search bar, then set media.gpu-process-decoder to false and see if you can reproduce the problem?

Yeap, this definitely seemed to do the trick. No more hanging or blank screens for now and transition time also down.

Michael, would you mind having a look?

I haven't really done work on the GPU decoder. I'm going to refer this to Matt.

Comment 8

[Ryan VanderMeulen [:RyanVM]]

I'm seeing this as well on my work X1 Carbon 6th Gen with Win10 1909 and latest updates and video drivers. LMK if there's anything I can do to help diagnose.

Comment 9

[Ryan VanderMeulen [:RyanVM]]

mozregression is pointing at bug 1547775 as the culprit.

Comment 10

[Ryan VanderMeulen [:RyanVM]]

Still reproducible with gfx.direct3d11.use-double-buffering set to false, though :(. Reproduces with and without WebRender. Also, setting media.gpu-process-decoder to false doesn't help for me.

For all pref changes, I restarted between attempts.

Nothing in the console when I run a debug build nor anything in the Browser Console either.

Comment 11

[Ryan VanderMeulen [:RyanVM]]

Attachment: My about:support

Comment 12

[Ryan VanderMeulen [:RyanVM]]

If I test release builds, the bug doesn't reproduce. However, looking at about:config, gfx.direct3d11.use-double-buffering was restricted back to Nightly-only via bug 1555956. If I manually flip the pref to true and restart, it reproduces.

Not sure why Nightly still reproduces with the pref set either way, though. But at least this doesn't appear to be actively affecting Release users from what I can see.

Comment 13

[Sotaro Ikeda [:sotaro]]

It might be similar to Bug 1573710.

Comment 14

[Jeff Muizelaar [:jrmuizel]]

Ryan, the original reported seemed to be seeing this on 69. To confirm, you do not see it on 69?

Comment 15

[Jeff Muizelaar [:jrmuizel]]

anishreddy20.ar, can you confirm that you see this issue on Firefox 69?

Comment 16

[Ryan VanderMeulen [:RyanVM]]

It only reproduces on Release 69 if you flip the gfx.direct3d11.use-double-buffering pref to true (since bug 1555956 made it false by default for release builds). It does reproduce on Nightly 69 builds.

Comment 17

[Ryan VanderMeulen [:RyanVM]]

Tracking this for Fx71 given bug 1580222.

Comment 18

[Anish]

(In reply to Jeff Muizelaar [:jrmuizel] from comment #15)

anishreddy20.ar, can you confirm that you see this issue on Firefox 69?

Confirmed, I still had that issue on 69 until after I changed the "media.gpu-process-decoder" config as referred above. For now the issue has gone.

Comment 19

[Anish]

(In reply to anishreddy20.ar from comment #18)

(In reply to Jeff Muizelaar [:jrmuizel] from comment #15)

anishreddy20.ar, can you confirm that you see this issue on Firefox 69?

Confirmed, I still had that issue on 69 until after I changed the "media.gpu-process-decoder" config as referred above. For now the issue has gone.

UPDATE: issue present in new update 69.0.3

Comment 20

[Pascal Chevrel:pascalc (PTO until April 26)]

Chunmin, given that double buffering is no longer disabled by default, this bug is going to hit users on the release channel, should that remain an unassigned P2? Should we revert bug 1580222? Thanks

Comment 21

[C.M.Chang[:chunmin]]

(In reply to Pascal Chevrel:pascalc from comment #20)

Chunmin, given that double buffering is no longer disabled by default, this bug is going to hit users on the release channel, should that remain an unassigned P2? Should we revert bug 1580222? Thanks

It seems the problem is in graphics instead of media, so I am going to change the component to graphic so graphic team can get the bug notification properly.

If setting gfx.direct3d11.use-double-buffering pref to false (reverting the bug 1580222) in release can prevent this problem, it might be a good way to do. However, from comment #10, I am not sure if it really can solve the problem. I guess graphic team may know how to deal with this better.

Comment 22

[Ryan VanderMeulen [:RyanVM]]

FWIW, this no longer reproduces for me, even on builds which previously did. Since then, I did install updated Intel graphics drivers, however (26.20.100.7323).

Comment 23

[Pascal Chevrel:pascalc (PTO until April 26)]

Bodgan, could your team try to reproduce this bug in the last beta and check if the bug is dependent on the intel graphics drivers? Thanks

Comment 24

[Bogdan Maris, Desktop QA]

(In reply to Pascal Chevrel:pascalc from comment #23)

Bodgan, could your team try to reproduce this bug in the last beta and check if the bug is dependent on the intel graphics drivers? Thanks

I tried to reproduce this on two machines (Surface Pro with CPU: Intel Core i5-3317U / GPU: Intel HD Graphics 4000 and Dell Inspiron 15 with CPU: Intel Core i5-8250U / GPU: Intel UHD Graphics 620) but I was unable to reproduce the issue (using both Firefox 69.0 or 71.0b11) even with older and newer drivers.

Comment 25

[Pascal Chevrel:pascalc (PTO until April 26)]

We have shipped our last beta for 71 and this seems like a hard case to reproduce so this is wontfix for 71.

Comment 26

[Jeff Muizelaar [:jrmuizel]]

anishreddy20.ar, can you still reproduce this problem on Firefox Beta or Firefox Nightly?

Comment 27

[Anish]

(In reply to Jeff Muizelaar [:jrmuizel] from comment #26)

anishreddy20.ar, can you still reproduce this problem on Firefox Beta or Firefox Nightly?

nope, this issue is not present on the stable build as well.

Comment 28

[Ryan VanderMeulen [:RyanVM]]

Sounds like this bug is WFM now. Feel free to reopen if it's still happening, though.

Comment 29

[Anish]

So it got fixed earlier on after v69 till v70.0 but recently started giving the same blank screen on YouTube as well. Also happens when you're switching back from Full-screen on Netflix/YouTube (either using cursor or touch)