(In reply to Olivier Fourdan from comment #20)
>=20
> I cannot load the file on nouveau where it was captured, it says
>=20
>  | 2 @0 eglGetPlatformDisplayEXT(platform =3D EGL_PLATFORM_GBM_KHR,
> native_display =3D 0x26926b0, attrib_list =3D {}) =3D 0x26d8250
>  | 2: warning: unsupported eglGetPlatformDisplayEXT call
> error: failed to create OpenGL 3.1 context.

Quick follow up on this, this is because of the way glamor works, it first
creates an EGL context with some config attributes (which include the OpenGL
version 3.1) and if it fails, it retries with no config attributes:

https://cgit.freedesktop.org/xorg/xserver/tree/glamor/glamor_egl.c=
#n819

or for Xwayland:

https://cgit.freedesktop.org/xorg/xserver/tree/hw/xwayla=
nd/xwayland-glamor.c#n310

So back to apitrace, as the config attributes specifies OpenGL 3.1, it fails
and apitrace just stops there. So I changed Xwayland to not do the first ca=
ll
(which on this HW returns NULL anyway) and now apitrace is a happy buddy, I=
 can
replay the trace on nouveau as well.

Same links, updated files:

=
https://people.freedesktop.org/~ofourdan/bug99400/Xwayland.log
https://people.freedesktop.org/~ofourdan/bug99400/Xwayland.trace

> For example frame 8932 (toward the end) is inter=
esting imho, [...]

Let's forget about this, now that the new trace can replay on both intel and
nouveau.

The problem I see is rather that I see no problem in apitrace, the frames l=
ook
fine, AFAICT.

And yet the rendering was wrong on screen when I captured the trace...