https://bugs.freedesktop.org/show_bug.cgi?id=91889
--- Comment #5 from Albert Freeman <albertwdfree...@gmail.com> --- The GPU has its own physical ram that is managed with a completely different system than system ram. There are actually two issues here. One is the bug in the game causing strange behavior. The other is the security issue that just so happens to (sometimes) arise due to that bug. This is probably not going to work, but try: export MESA_EXTENSION_OVERRIDE=GL_ARB_gpu_shader5 then run the game in the same console window. That seems to get rid of a rather critical warning when I replay the trace. Strange thing is, when I replay this on mesa and catalyst, the same visual corruption occurs (in the areas I can remember, exactly the same). Though catalyst shows no warnings/errors but mesa does. This shouldn't happen as apitrace simply records GL commands/data before they reach the driver. When replayed they get sent to my driver for display. Someone on irc commented that apitrace does not always capture all data needed to display the replay flawlessly. However the corruption seems to be in areas which shouldn't (in normal circumstances) be affected by missing data (as far as I know) (e.g. empty sky OR big things crosscutting many different bits of geometry/UI, like rectangles). -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug.
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
