diff options
| author | jamescook@chromium.org <jamescook@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-04-24 17:45:12 +0000 |
|---|---|---|
| committer | jamescook@chromium.org <jamescook@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-04-24 17:45:12 +0000 |
| commit | bfcd88899348e8d71fa8b62811359d7cf8c759d9 (patch) | |
| tree | 096ca386486150c045adfa274e652d3f1f696764 /tools/gdb/gdb_chrome.py | |
| parent | de645437b15b4999490d8a58e13a5d512827778f (diff) | |
| download | chromium_src-bfcd88899348e8d71fa8b62811359d7cf8c759d9.zip chromium_src-bfcd88899348e8d71fa8b62811359d7cf8c759d9.tar.gz chromium_src-bfcd88899348e8d71fa8b62811359d7cf8c759d9.tar.bz2 | |
views: Add class names to views paint trace events
We're trying to track down a view that is painting at 60 Hz, but the problem
only reproduces in official canary builds. The class names may help us find
the view in question.
BUG=227375
TEST=manual, run about:tracing, capture a trace, click on a View::Paint task and note that there is a "class" data field
Review URL: https://chromiumcodereview.appspot.com/14149012
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@196176 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'tools/gdb/gdb_chrome.py')
0 files changed, 0 insertions, 0 deletions