1663250 - [Wayland] start failure: `[GFX1-]: Failed to create EGLContext!` on 32 bit llvmpipe

Status: RESOLVED WORKSFORME

(Core :: Graphics: WebRender, defect)

Description

[Paul Menzel]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:80.0) Gecko/20100101 Firefox/80.0

Steps to reproduce:

On Debian Sid/unstable run enlightenment_start on VT, and then start Firefox 80.0.1 with MOZ_ENABLE_WAYLAND=1 MOZ_WEBRENDER=1 firefox from a terminal.

Actual results:

Firefox crashes with:

[GFX1-]: Failed to create EGLContext!: 0x3009
[GFX1-]: Failed to link shader program: cs_clip_rectangle
error: Too many vertex shader texture samplers

[2020-09-05T10:30:47Z ERROR webrender::device::gl] Failed to link shader program: cs_clip_rectangle
error: Too many vertex shader texture samplers

ExceptionHandler::GenerateDump cloned child 1054
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
Exiting due to channel error.

Expected results:

Firefox should start normally.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Comment 2

[Miko Mynttinen]

Thank you for the report Paul.

Does this only happen with Wayland and/or WebRender enabled? To help us narrow this done further, could you please attach the output from about:support in this bug? This might be a graphics driver issue.

1. Enter about:support into the address bar.
2. Click the Copy text to clipboard button.
3. Paste the clipboard contents into a text editor like Notepad, and save the file.
4. Click the Attach New File button above the description here to upload the file.

Comment 3

[Paul Menzel]

Attachment: `about:support` with `MOZ_ENABLE_WAYLAND=1 firefox`

(In reply to Miko Mynttinen [:miko] from comment #2)

Thank you for the report Paul.

Thank you for the follow-up.

Does this only happen with Wayland and/or WebRender enabled?

It only happens with WebRender enabled. MOZ_ENABLE_WAYLAND=1 firefox starts, i. e. it does not crash, but it’s not very usable, as there are a lot of artifacts from previous images (scrolling, switching tabs, windows) or the mouse pointer.

To help us narrow this done further, could you please attach the output from about:support in this bug? This might be a graphics driver issue.

1. Enter about:support into the address bar.
2. Click the Copy text to clipboard button.
3. Paste the clipboard contents into a text editor like Notepad, and save the file.
4. Click the Attach New File button above the description here to upload the file.

Done. Please also note the crash stats:

1. https://crash-stats.mozilla.org/report/index/9b35bd8b-7c0e-4d6d-9294-5a9810200910
2. https://crash-stats.mozilla.org/report/index/abc4bb17-8ecf-4bb1-887a-dc4ed0200911

Doing this, I saw that on i386, Debian still has Firefox 79.0.

80.0.1-1: amd64 arm64 armhf mips64el s390x
79.0-1: i386 ppc64el

Sorry for missing that.

Comment 4

[Paul Menzel]

It still happens with Nightly (82.0a1).

1. https://crash-stats.mozilla.org/report/index/42f0de4d-763e-49ec-9db2-3d38b0200911

Comment 5

[Paul Menzel]

By the way, it’s unrelated to the window manager. It also happens with Weston.

Comment 6

[Darkspirit]

Linux i686; rv:79.0
WebGL 1 Driver Version: 3.0 Mesa 20.1.7
WebGL 2 Driver Version: OpenGL ES 3.1 Mesa 20.1.7

So it's EGL (Wayland) with 32 bit llvmpipe: Yours seems to support OGL 3.0/EGL (bug 1474281), which is not enough, so it should fall back to GLES/EGL, which should work as GLES 3.1 is advertised.

Window Protocol: wayland/drm

(Could DMABUF cause problems with llvmpipe?)

Please also attach about:support of Nightly with EGL on Xwayland:
$ MOZ_X11_EGL=1 MOZ_WEBRENDER=1 path/to/firefox

Comment 7

[Darkspirit]

Typo: I meant MOZ_X11_EGL=1

Comment 8

[Paul Menzel]

Attachment: `about:support` with `MOZ_X11_EGL=1 MOZ_WEBRENDER=1 firefox` with Nightly from 21.9.20

Comment 9

[Paul Menzel]

I do not know, what change fixed it, but it works with Nightly 83.0a1 (20200927094310).

Comment 10

[Paul Menzel]

I updated to Mesa 20..1.9 and also to the current Nightly, so no idea what changed the behavior. The problem is still there, but a little different, and it does not happen when using Mesa’s radeonsi.

So console message are not shown anymore, and a crash report was uploaded 1.

Comment 11

[Igor Kovalenko]

I just traced similar crash on a system with older radeon card (mesa r600 driver) trying to reproduce bug 1673939 with software renderer to a bug in mesa https://gitlab.freedesktop.org/mesa/mesa/-/issues/3613

If you see that DRAW_USE_LLVM=no is set in the environment, this is the same issue.
It is still to be fixed in mesa-20.2.2 - unexpected environment variable is leaking into userspace causing llvmpipe to crash

src/gallium/drivers/r600/r600_pipe_common.c:       setenv("DRAW_USE_LLVM", "no", 0);

There is a workaround to unset the offending variable before running your test with software renrerer.

Like the following in the terminal window:

unset DRAW_USE_LLVM
run your firefox test

Please give it a go and see if that fixes the issue.

Comment 12

[Robert Mader [:rmader]]

Paul, can you still reproduce this with recent mesa?

Comment 13

[BugBot [:suhaib / :marco/ :calixte]]

Closing because no crashes reported for 12 weeks.