diff options
| author | nduca@chromium.org <nduca@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-07-19 02:22:10 +0000 |
|---|---|---|
| committer | nduca@chromium.org <nduca@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-07-19 02:22:10 +0000 |
| commit | 96d51c626fc60f60f4909afa3b44e6b62f57881c (patch) | |
| tree | 120a5ee31fdd3b62edc0417a1c759e55e878b19e /content/browser/renderer_host/java | |
| parent | c588c3a1163f2b668df854f2fe6038eb1538a814 (diff) | |
| download | chromium_src-96d51c626fc60f60f4909afa3b44e6b62f57881c.zip chromium_src-96d51c626fc60f60f4909afa3b44e6b62f57881c.tar.gz chromium_src-96d51c626fc60f60f4909afa3b44e6b62f57881c.tar.bz2 | |
Remove traces on didInvalidate and scheduleComposite
This is wholly inappropriate. Way too high overhead. Better to delete and then
do followup bug if someone asks to issue them on the first trace. But that is
actually pretty tricky to do, so I'm suggesting we just nuke them. From orbit.
R=piman
Review URL: https://chromiumcodereview.appspot.com/19732002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212512 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/browser/renderer_host/java')
0 files changed, 0 insertions, 0 deletions