summaryrefslogtreecommitdiffstats
path: root/win8
diff options
context:
space:
mode:
authorvadimt <vadimt@chromium.org>2015-01-16 17:28:06 -0800
committerCommit bot <commit-bot@chromium.org>2015-01-17 01:29:55 +0000
commit3549b9a1e5b4698865c91458e6255231fdc4cba9 (patch)
treec7fda936c86234fa218b47449bc0a3e75467e2d4 /win8
parent8ce46c7881a3296187c7dd27afb581f84f4b27a7 (diff)
downloadchromium_src-3549b9a1e5b4698865c91458e6255231fdc4cba9.zip
chromium_src-3549b9a1e5b4698865c91458e6255231fdc4cba9.tar.gz
chromium_src-3549b9a1e5b4698865c91458e6255231fdc4cba9.tar.bz2
Instrumenting all wndprocs to find jank.
PeekMessage calls are still the top source of jank. The theory is that they invoke some synchronous message processing, and this causes jank. I realized that I didn't instrument all wndprocs, which I'm doing now. BUG=440919 Review URL: https://codereview.chromium.org/850213002 Cr-Commit-Position: refs/heads/master@{#312004}
Diffstat (limited to 'win8')
-rw-r--r--win8/metro_driver/metro_driver_win7.cc5
1 files changed, 5 insertions, 0 deletions
diff --git a/win8/metro_driver/metro_driver_win7.cc b/win8/metro_driver/metro_driver_win7.cc
index 7ae32cc..d5496d6 100644
--- a/win8/metro_driver/metro_driver_win7.cc
+++ b/win8/metro_driver/metro_driver_win7.cc
@@ -7,6 +7,7 @@
#include <shobjidl.h>
#include "base/logging.h"
+#include "base/profiler/scoped_tracker.h"
#include "ui/gfx/geometry/safe_integer_conversions.h"
#include "ui/gfx/win/msg_util.h"
@@ -1004,6 +1005,10 @@ class CoreWindowEmulation
LRESULT CALLBACK WndProc(HWND hwnd, UINT message,
WPARAM wparam, LPARAM lparam) {
+ // TODO(vadimt): Remove ScopedTracker below once crbug.com/440919 is fixed.
+ tracked_objects::ScopedTracker tracking_profile(
+ FROM_HERE_WITH_EXPLICIT_FUNCTION("440919 MetroDriver WndProc"));
+
PAINTSTRUCT ps;
HDC hdc;
switch (message) {