From 3549b9a1e5b4698865c91458e6255231fdc4cba9 Mon Sep 17 00:00:00 2001 From: vadimt Date: Fri, 16 Jan 2015 17:28:06 -0800 Subject: 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} --- win8/metro_driver/metro_driver_win7.cc | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'win8') 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 #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) { -- cgit v1.1