Closed Bug 1871960 Opened 9 months ago Closed 6 months ago

Intermittent canvas/784573-1.html == canvas/784573-1-ref.html | single tracking bug

Categories

(Core :: Graphics, defect, P5)

defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: intermittent-bug-filer, Unassigned)

References

Details

(Keywords: intermittent-failure, intermittent-testcase)

(Context: the push here was a try push for "staging release: 123.0b12")

This is probably a graphics issue, possibly something having gone wrong with the GPU process. The log shows a bunch of lines like this earlier on:

[task 2023-12-26T12:08:26.321Z] 12:08:26     INFO - [GPU 3576, Renderer] WARNING: Failed to make GL context current!: file /builds/worker/checkouts/gecko/gfx/gl/GLContextProviderEGL.cpp:463
[task 2023-12-26T12:08:26.321Z] 12:08:26     INFO - EGL Error: 0x3009
[task 2023-12-26T12:08:26.322Z] 12:08:26     INFO - [GPU 3576, Renderer] WARNING: GLContext::InitWithPrefix failed!: file /builds/worker/checkouts/gecko/gfx/gl/GLContext.cpp:337
[task 2023-12-26T12:08:26.322Z] 12:08:26     INFO - Destroying context 06F73000 surface 05182280 on display 06F4CC00
[task 2023-12-26T12:08:26.323Z] 12:08:26     INFO - [GPU 3576, Renderer] WARNING: Failed to create GLContext from PBuffer: file /builds/worker/checkouts/gecko/gfx/gl/GLContextProviderEGL.cpp:1193

Possibly related to bug 1858436 which is also about issues with the GPU process that we happen to be hitting on release/beta runs in particular.

Component: Layout: Images, Video, and HTML Frames → Graphics
See Also: → 1858436
Status: NEW → RESOLVED
Closed: 8 months ago
Resolution: --- → INCOMPLETE
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---

The first mention of "GPU" in the log for comment 4 is this, at startup-time:

[task 2024-02-22T23:27:50.562Z] 23:27:50     INFO - Crash Annotation GraphicsCriticalError: |[0][GFX1-]: Killing GPU process due to IPC reply timeout (t=1201.63) [GFX1-]: Killing GPU process due to IPC reply timeout
[task 2024-02-22T23:27:50.563Z] 23:27:50     INFO - Crash Annotation GraphicsCriticalError: |[0][GFX1-]: Killing GPU process due to IPC reply timeout (t=1201.63) |[1][GFX1-]: Fallback WR to SW-WR + D3D11 (t=1201.63) [GFX1-]: Fallback WR to SW-WR + D3D11
[task 2024-02-22T23:28:01.016Z] 23:28:01     INFO - Crash Annotation GraphicsCriticalError: |[0][GFX1-]: Killing GPU process due to IPC reply timeout (t=1201.63) |[1][GFX1-]: Fallback WR to SW-WR + D3D11 (t=1201.63) |[2][GFX1-]: Killing GPU process due to IPC reply timeout (t=1306.16) [GFX1-]: Killing GPU process due to IPC reply timeout
[task 2024-02-22T23:28:01.019Z] 23:28:01     INFO - Crash Annotation GraphicsCriticalError: |[0][GFX1-]: Killing GPU process due to IPC reply timeout (t=1201.63) |[1][GFX1-]: Fallback WR to SW-WR + D3D11 (t=1201.63) |[2][GFX1-]: Killing GPU process due to IPC reply timeout (t=1306.16) |[3][GFX1-]: Fallback SW-WR + D3D11 to SW-WR (t=1306.16) [GFX1-]: Fallback SW-WR + D3D11 to SW-WR

So this seems to be a case where the GPU process died, similar to comment 1. Though in this case, it was actively killed after a timeout.

Given that this was an ASAN build, I wonder if the "IPC reply timeout" here was just ASAN slowing things down, rather than anything actually going wrong that would merit killing the GPU process...

From my memory that is how it happens in general (including non-ASAN) on Windows jobs where we lose the gpu process: a timeout.

Status: REOPENED → RESOLVED
Closed: 8 months ago6 months ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.