Closed Bug 1394108 Opened 7 years ago Closed 7 years ago

Third party compositor state changes crash open tabs' rendering engine(s)

Categories

(Core :: Widget: Gtk, defect)

defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1377950

People

(Reporter: obscurecolin, Unassigned)

Details

(Keywords: crash)

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36

Steps to reproduce:

On my linux system, I often change the state of my third-party compositor, compton. 
These changes, as of 55.*.* (most recently tested on 55.0.3), now cause open tabs rendering to simply crash (go blank, even a refresh doesn't prompt it to re-render).

You can observe what I mean from this video I recorded:
https://vimeo.com/231154755

So, by simply changing the state of the compositor daemon (via piped commands), Firefox. This error does not occur in 54.*.* (I downgraded and only tested on 54.0.1).


Actual results:

Open tabs stop being rendered and simply show white (sometimes with a spinning loading icon in the centre).


Expected results:

They should have kept being rendered regardless of the state of the external compositor (as they do in previous releases).
Component: Untriaged → Widget: Gtk
Keywords: crash
Product: Firefox → Core
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.