xpra icon
Bug tracker and wiki

Changes between Version 7 and Version 8 of Debugging/OpenGL


Ignore:
Timestamp:
08/12/15 06:31:58 (4 years ago)
Author:
Antoine Martin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Debugging/OpenGL

    v7 v8  
    77[[BR]]
    88
     9The first step is to run the client with {{{-d opengl}}}, this should log a lot more information about opengl calls and is often enough to spot the source of the problem
    910
    10 Whenever you encounter problems with client-side `OpenGL` rendering, for example with `OpenGL` error messages, crashes, or visual artifacts, there are some specific steps to take to investigate. The *`Apitrace`* tool will get a dump of the `OpenGL` command stream, allowing it to be sent to the developers for replaying and investigation.
     11Then there is also the environment variable {{{XPRA_OPENGL_DEBUG=1}}} which will enable the {{{GREMEDY}}} extension if present.
     12
     13If these options are not sufficient to identify the source of the problem, you can use other tools to dig into the opengl rendering:
     14* Apitrace (see below)
     15* [https://github.com/ValveSoftware/vogl vogl]
     16* [https://developer.nvidia.com/linux-graphics-debugger NVidia's Linux Graphics Debugger]
    1117}}}
    1218
    1319{{{#!div class="box"
    14 == Installation ==
     20== Apitrace Installation ==
     21
     22The *`Apitrace`* tool will get a dump of the `OpenGL` command stream, allowing it to be sent to the developers for replaying and investigation.
    1523
    1624* On Linux:
     
    2533
    2634{{{#!div class="box"
    27 == Trace generation ==
     35== Apitrace Usage ==
    2836
    2937This trace will enable you to replay the actions of the client without having to re-run it; giving you additional error tracing, ability to send the trace to another person, and ability to replay the exact same steps every time.