Random crashes in ca. 1min to 1h on Intel laptop with igpu driver (Iris) calling abort() / SIGABRT about mpvpaper

[GhostNaN]

Considering it crashed at:

mpvpaper/src/main.c

Lines 141 to 144 in 666f4c9

	// Display frame
	if (!eglSwapBuffers(egl_display, egl_surface))
	cflp_error("Failed to swap egl buffers 0x%X", eglGetError());
	}

And didn't just throw back an error message.
I want to say mpvpaper didn't do anything wrong here.

Also, it went from having a pointer to the display, to not?
#10 0x00007f25dede6ae8 in dri2_swap_buffers (disp=0x5568aa8415a0, surf=0x5568aaa3cbd0) at ../mesa-main/src/egl/drivers/dri2/egl_dri2.c:2042
#11 0x00007f25dedd5825 in eglSwapBuffers (dpy=<optimized out>, surface=0x5568aaa3cbd0) at ../mesa-main/src/egl/main/eglapi.c:1421

But I'm not a graphics expert, go ahead and take this upstream.
Because even if it is mpvpaper, they might be able to guide us in the right direction.

Thank you for your excellent debug logs and effort!

[gergo-salyi]

I'm closing this because since mpvpaper commit 781320f this crash is extremely rare (happened only once for me since) and thus not reproducible.

(For the record: the crash likely happened with two Iris driver I915_GEM_EXECBUFFER2 ioctls which by random chance came within ~5us close in time, caused one of them to fail with errno ENOSPC which Mesa chooses to abort on. The leading cause to this event remains unknown, and could be anywhere in the whole application + libraries. The Mesa issue I reported is here although Mesa devs were not really interested.)

Moreover a week ago I saw a similar backtrace for a vanilla mpv crashing. Likely this situation was not and is not mpvpaper's fault.

[GhostNaN]

Thank you for your investigation into this issue!