New issue
Advanced search Search tips

Issue 888169 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

No longer able to use profiling on the gpu process

Project Member Reported by enne@chromium.org, Sep 21

Issue description

gn args out/profile
  use_goma = true
  enable_nacl = false
  is_debug = false
  is_component_build = true
  enable_profiling = true
  enable_callgrind = true

ninja -C out/profile -j500 -l20 chrome && out/profile/chrome --enable-gpu-rasterization --enable-oop-rasterization --enable-profiling --profiling-at-start=gpu-process --no-sandbox --profiling-flush "http://browserbench.org/MotionMark/developer.html?suite-name=Animometer&test-name=Multiply&complexity=1000&test-interval=900&display=minimal&tiles=big&controller=fixed&frame-rate=50&kalman-process-error=1&kalman-measurement-error=4&time-measurement=performance"

I get a profile that looks like the attached.  Renderer process profiles look normal.  This has worked for me in the past.
 
profile002.png
20.9 KB View Download

Sign in to add a comment