add a human-readable explanation to allow the trace to show why the command buffer was synchronously flushed; This is handy to track down why we're experiencing long command buffer flushes on Android sometimes with GPU rasterization

BUG=

Review URL: https://codereview.chromium.org/132243002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@247514 0039d316-1c4b-4281-b951-d872f2087c98

2 files changed, 3 insertions, 0 deletions

diff --git a/gpu/command_buffer/client/gles2_implementation.cc b/gpu/command_buffer/client/gles2_implementation.cc
index 0133311..2f31942 100644
--- a/gpu/command_buffer/client/gles2_implementation.cc
+++ b/gpu/command_buffer/client/gles2_implementation.cc
@@ -868,6 +868,7 @@ void GLES2Implementation::Finish() {
 
 void GLES2Implementation::ShallowFinishCHROMIUM() {
   GPU_CLIENT_SINGLE_THREAD_CHECK();
+  TRACE_EVENT0("gpu", "GLES2::ShallowFinishCHROMIUM");
   // Flush our command buffer (tell the service to execute up to the flush cmd
   // and don't return until it completes).
   helper_->CommandBufferHelper::Finish();
diff --git a/gpu/command_buffer/client/transfer_buffer.cc b/gpu/command_buffer/client/transfer_buffer.cc
index c4b84a1..00d1f48 100644
--- a/gpu/command_buffer/client/transfer_buffer.cc
+++ b/gpu/command_buffer/client/transfer_buffer.cc
@@ -6,6 +6,7 @@
 
 #include "gpu/command_buffer/client/transfer_buffer.h"
 
+#include "base/debug/trace_event.h"
 #include "base/logging.h"
 #include "gpu/command_buffer/client/cmd_buffer_helper.h"
 
@@ -53,6 +54,7 @@ bool TransferBuffer::Initialize(
 
 void TransferBuffer::Free() {
   if (HaveBuffer()) {
+    TRACE_EVENT0("gpu", "TransferBuffer::Free");
     helper_->Finish();
     helper_->command_buffer()->DestroyTransferBuffer(buffer_id_);
     buffer_id_ = -1;