![]() You can also see them on standard output if Chromium is run from the command line on Linux/Mac. You can see these by navigating to about:gpu. The GPU process logs many errors and warnings. glVertexAttribPointer(0, 3, GL_FLOAT, GL_FALSE, 0, 0) The output looks like this: glUseProgram(3) It's typically necessary to specify the -enable-logging=stderr flag as well: -enable-gpu-client-logging -enable-logging=stderr You can also use this flag in a release build by specifying the GN argument: enable_gpu_client_logging=true ![]() ![]() (From the point of view of a GPU client, it's calling OpenGL ES functions - but the real driver calls are made in the GPU process.) If you are trying to track down a bug in a GPU client process (compositing, WebGL, Skia/Ganesh, Aura), then in a debug build you can use the -enable-gpu-client-logging flag, which will show every GL call sent to the GPU service process. Renderer Process Code -enable-gpu-client-logging ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |