Closed
Bug 1590498
Opened 5 years ago
Closed 5 years ago
[Wayland] Hang with "We don't have EGLSurface to draw into. Called too early?"
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
RESOLVED
FIXED
mozilla72
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox67 | --- | unaffected |
firefox68 | --- | unaffected |
firefox69 | --- | unaffected |
firefox70 | --- | unaffected |
firefox71 | --- | unaffected |
firefox72 | --- | fixed |
People
(Reporter: grayshade, Assigned: sotaro)
References
(Blocks 2 open bugs, Regression)
Details
(Keywords: regression)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
Ran Firefox Wayland on Gnome / Arch Linux.
Actual results:
It hangs every 10 minutes or so, and spits out [GFX1-]: We don't have EGLSurface to draw into. Called too early?
in the console.
Expected results:
No hang. It used to work. This regressed around 22 Oct.
Reporter | ||
Updated•5 years ago
|
Component: Untriaged → Graphics
OS: Unspecified → Linux
Product: Firefox → Core
Hardware: Unspecified → Desktop
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
It might be regressed by Bug 1584511, though I did not see the problem with Wayland on Ubuntu 18.04.
Assignee | ||
Updated•5 years ago
|
Component: Graphics → Graphics: WebRender
Assignee | ||
Comment 2•5 years ago
|
||
I could reproduce the problem when Firefox profiler addon window is opened.
Assignee | ||
Updated•5 years ago
|
Assignee: nobody → sotaro.ikeda.g
Assignee | ||
Comment 3•5 years ago
|
||
Bug 1584511 had 2 problems.
- nsWindow::HideWaylandWindow() is called just during closing a window.
- GPUProcessManager::Get()->ResetCompositors() updates all compositor. But it does not set "mCompositorInitiallyPaused = true" to all widget.
Assignee | ||
Comment 4•5 years ago
|
||
Bug 1584511 was backed-out.
https://hg.mozilla.org/mozilla-central/rev/00e66d88797b
Updated•5 years ago
|
Keywords: regression
Assignee | ||
Comment 5•5 years ago
|
||
Backout Bug 1584511 addressed the problem for me.
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Updated•5 years ago
|
status-firefox67:
--- → unaffected
status-firefox68:
--- → unaffected
status-firefox69:
--- → unaffected
status-firefox70:
--- → unaffected
status-firefox71:
--- → unaffected
status-firefox72:
--- → fixed
status-firefox-esr68:
--- → unaffected
Target Milestone: --- → mozilla72
Updated•2 years ago
|
Has Regression Range: --- → yes
You need to log in
before you can comment on or make changes to this bug.
Description
•