Unfortunately openmw is only a game engine and the game data or assets are
not included which are required for using it. This could make testing it
morecomplicated, however I can build mesa myself and test any patches if that
helps.
If the game data is provided this is relatively easy to reproduce at least with
nouveauand DRI3 while LIBGL_DRI3_DISABLE=1is able to launch and play the game
successfully.
The previous patch avoids the crash by blocking the problematic custom mouse
cursor
used by openmw for the menus which is then reduced to a tiny ".." and is hard
to spot.
Hunter
From: Marek Olšák <mar...@gmail.com>
To: Tobias Klausmann <tobias.johannes.klausm...@mni.thm.de>
Cc: "mesa-dev@lists.freedesktop.org" <mesa-dev@lists.freedesktop.org>;
ovarieg...@yahoo.com
Sent: Thursday, August 18, 2016 1:40 PM
Subject: Re: [Mesa-dev] [RFC] st: guard against NULL pipe_surface
On Thu, Aug 18, 2016 at 2:41 PM, Tobias Klausmann
<tobias.johannes.klausm...@mni.thm.de> wrote:
> I have no test case per se, but orbea (in CC) noted in IRC:
>
> Start OpenMW with DRI3 -> Crash [1]
>
> Start OpenMW with DRI2 -> no crash,
>
> So i fear it is somewhere in our DRI3 path. Anyway a guard seems reasonable
> to harden release builds against this. Maybe not at this place but central
> in update_framebuffer_size().
Yeah, it would be very useful if we could reproduce this somehow.
Marek
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
