[Wayland Proxy] Fail if we can't connect to compositor for some time
Categories
(Core :: Widget: Gtk, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox125 | --- | fixed |
People
(Reporter: stransky, Assigned: stransky)
References
(Blocks 1 open bug)
Details
Attachments
(3 files)
Fail if we can't connect to compositor for some time.
Assignee | ||
Comment 1•11 months ago
|
||
Updated•11 months ago
|
Comment 2•11 months ago
|
||
I see this bug from the Wayland metabug, got a question: what would be the result of this in the case of a system under heavy load and temporarily unresponsive?
(Wondering, as I've a bug regarding some Firefox crashes on rare occasions, and that might be one of the causes)
Assignee | ||
Comment 3•11 months ago
|
||
(In reply to Clément Lefèvre from comment #2)
I see this bug from the Wayland metabug, got a question: what would be the result of this in the case of a system under heavy load and temporarily unresponsive?
(Wondering, as I've a bug regarding some Firefox crashes on rare occasions, and that might be one of the causes)
If we fail to connect to compositor for some time it usually means the connection is already dead as Gtk display init doesn't wait so long.
If Gtk display init fails at _gdk_wayland_display_open() (wl_display_roundtrip() returns -1) Gtk silently switches to X11 and proxy us not used at all.
I think in such case we should remove the proxy actually.
Assignee | ||
Comment 4•11 months ago
|
||
If Gtk switched from Wayland to X11 during display open phase, do that change on browser side too.
It may happen if WAYLAND_DISPLAY is wrongly set or compositor is slow or so.
Depends on D203249
Assignee | ||
Comment 5•11 months ago
|
||
Depends on D203259
Assignee | ||
Updated•11 months ago
|
Comment 7•11 months ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/2c65e9ed99a1
https://hg.mozilla.org/mozilla-central/rev/3645593a0f45
https://hg.mozilla.org/mozilla-central/rev/8a586af3529e
Description
•