chromium/src
0
Fork 0
Code Activity

Add documentation of --enable-gpu-service-tracing flag.

Browse Source 
Bug: b/189215577
Change-Id: I0f299703b109bf178f6c536f5cd9d00e5a1d680a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2953111
Auto-Submit: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Commit-Queue: Zhenyao Mo <zmo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#891408}
This commit is contained in:
Kenneth Russell
2021-06-10 22:11:17 +00:00
committed by Chromium LUCI CQ
parent d3e45f1b46
commit d2a12773e7
1 changed files with 10 additions and 1 deletions

11
docs/gpu/debugging_gpu_related_code.md

@ -237,6 +237,15 @@ If you see this message in `about:gpu` or your console and you didn't cause it
directly (by calling `glLoseContextCHROMIUM`) and it's something other than 5
that means there's likely a bug. Please file an issue at <http://crbug.com/new>.
## Tracing OpenGL calls
Passing the command line flag `--enable-gpu-service-tracing` causes
the GPU process to emit one trace event per OpenGL API call. (See
"Debugging Performance", below.) This is useful when trying to
understand where the expensive operations are in a given set of work
sent from a renderer process to the GPU process, and processed
underneath `CommandBufferService::PutChanged`.
## Debugging Performance
If you have something to add here please add it. Most perf debugging is done
@ -253,4 +262,4 @@ printf("elapsedTime = %f\n", end - start);
**will not** give you meaningful results.
[See Trace Event Profiling for details]: https://sites.google.com/a/chromium.org/dev/developers/how-tos/trace-event-profiling-tool
[Trace Event Profiling]: https://sites.google.com/a/chromium.org/dev/developers/how-tos/trace-event-profiling-tool