158 | | 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. |
159 | | The most important thing is to build the tool Apitrace (https://github.com/apitrace/apitrace) according to the documentation https://github.com/apitrace/apitrace/blob/master/INSTALL.markdown, and use it on Xpra to get a full trace. |
| 158 | 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. |
| 159 | |
| 160 | === Installation of Apitrace === |
| 161 | |
| 162 | ==== On Linux ==== |
| 163 | |
| 164 | Download Apitrace (https://github.com/apitrace/apitrace), build it according to the documentation https://github.com/apitrace/apitrace/blob/master/INSTALL.markdown |
| 165 | |
| 166 | ==== On Windows ==== |
| 167 | |
| 168 | You can use pre-built binaries found at http://people.freedesktop.org/~jrfonseca/apitrace/ Try to always use the latest version and fallback to an older one if it doesn't work. |
| 169 | |
| 170 | === Trace generation === |