1815766 - Crash in GL: Caught GL error 507 (GL_CONTEXT_LOST) at flush

Status: REOPENED

(Core :: Graphics, defect, P3)

Description

[Randell Jesup [:jesup] (needinfo me)]

Attachment: gl_crash.txt

Local build based off m-c, with no graphics-related changes (WebTransport work). It's always possible a memory-trashing from the new code happened, though I think unlikely.
I was running the demo. Not certain exactly what I was doing when it crashed (editing or hitting Run to see if there was a syntax error)

Linux Fedora 36, NVidia proprietary drivers v515.57

Crashed in a debug build working with https://jsfiddle.net/c7Lbgzhd/1/

Comment 1

[Brad Werth [:bradwerth]]

Will discuss in gfx-triage.

Comment 2

[Brad Werth [:bradwerth]]

It seems like we won't be able to do much with this without a reproducible testcase. Ashley, you have a NVidia Linux? Can you reproduce with the jsfiddle in comment 0.

Comment 3

[Ashley Hale [:ahale]]

I don't currently have nvidia proprietary drivers set up on any of my linux machines, I'll try to find the spare cycles to repro this.

Comment 4

[Kelsey Gilbert [:jgilbert]]

0x0507 is CONTEXT_LOST: https://kdashg.github.io/misc/gl/search-headers.html#str=0x0507
This looks like a bug in Gleam. We shouldn't crash (even in debug builds) when we get CONTEXT_LOST.