Firefox goes blank after mpv and ffplay fullscreen

UNCONFIRMED
Unassigned

Status

()

P3
normal
UNCONFIRMED
a year ago
11 months ago

People

(Reporter: magpie240, Unassigned, NeedInfo)

Tracking

55 Branch
Points:
---

Firefox Tracking Flags

(firefox55 wontfix, firefox56 wontfix, firefox57 fix-optional)

Details

(Whiteboard: [gfx-noted])

Attachments

(1 attachment)

(Reporter)

Description

a year ago
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0
Build ID: 20170727121554

Steps to reproduce:

Firefox running normally. Start watching video fullscreen in mpv or ffplay. Returned from fullscreen.


Actual results:

Firefox pages were blank. Quick vid here: https://sta.sh/071s9oq5cxv 


Expected results:

Pages should have still been visible. Disabling hardware accel seems to solve. Issue noticed in 55b12 and 56a.
Component: Untriaged → Audio/Video: Playback
Product: Firefox → Core

Comment 1

a year ago
I have the same problem on Gentoo with release version of firefox-55. After I start mpv I see that current tab in Mozilla flickers and goes blank in a second.
Same on closing mpv window.

Comment 2

a year ago
The problem remains in 55.0.1
(In reply to magpie240 from comment #0)
> Disabling hardware accel seems to solve.

This is therefore a graphics issue and likely a dupe, since HW accel isn't enabled by default.
Component: Audio/Video: Playback → Graphics

Comment 4

a year ago
same in 55.0.2 and 55.0.3

I've disabled "Use hardware acceleration when available" in General -> Performance settings, but it didn't help me.
Ryan, can you reproduce this?
status-firefox55: --- → wontfix
status-firefox56: --- → wontfix
status-firefox57: --- → fix-optional
Flags: needinfo?(rhunt)
Priority: -- → P3
Whiteboard: [gfx-noted]

Comment 6

11 months ago
(In reply to magpie240 from comment #0)
> User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:55.0) Gecko/20100101
> Firefox/55.0
> Build ID: 20170727121554
> 
> Steps to reproduce:
> 
> Firefox running normally. Start watching video fullscreen in mpv or ffplay.
> Returned from fullscreen.
> 
> 
> Actual results:
> 
> Firefox pages were blank. Quick vid here: https://sta.sh/071s9oq5cxv 
> 
> 
> Expected results:
> 
> Pages should have still been visible. Disabling hardware accel seems to
> solve. Issue noticed in 55b12 and 56a.

I'm not able to reproduce this. Tried to reproduce this on Arch linux with 55.0 and Nightly then watching a video in fullscreen with ffplay and then closing out of it. I attempted with and without 'layers.acceleration.force-enabled'.

I tried to view the video you linked to but it's no longer there. Could you reupload somewhere so I can see what's happening? Also it could be helpful if you posted the graphics section of about:support.

If you'd like, you can also give mozregression a try to see when this became broken. That'd also help us out. [1]

[1] http://mozilla.github.io/mozregression/
Flags: needinfo?(rhunt) → needinfo?(magpie240)

Comment 7

11 months ago
Created attachment 8907722 [details]
Graphics section of about:support

I've switched to binary version (instead of using sources) of Firefox (I think it's official one) and I still have this problem.

Graphics section of about:support is attached

Comment 8

11 months ago
I've checked older and beta versions and the bug was present in 55.0b1

And since 55.x branch is buggy for me I've decided to check 56.0b10 - active tab noticeably blinks on opening/closing mpv video, but doesn't go blank in the end. 

So, kinda resolved in upcoming version.

Comment 9

11 months ago
(In reply to Alex from comment #8)
> I've checked older and beta versions and the bug was present in 55.0b1
> 
> And since 55.x branch is buggy for me I've decided to check 56.0b10 - active
> tab noticeably blinks on opening/closing mpv video, but doesn't go blank in
> the end. 
> 
> So, kinda resolved in upcoming version.

My guess then is that this is a dupe of bug 1377950, which is resolved in 56 (soon to be released).

The fix for it will still cause content to flash white for a second, which you noticed. That's bug 1396418.

I'll mark this resolved if the reporter can confirm it's fixed in the current beta of 56.
You need to log in before you can comment on or make changes to this bug.