diff options
| author | vadimt <vadimt@chromium.org> | 2015-01-16 17:28:06 -0800 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2015-01-17 01:29:55 +0000 |
| commit | 3549b9a1e5b4698865c91458e6255231fdc4cba9 (patch) | |
| tree | c7fda936c86234fa218b47449bc0a3e75467e2d4 /ui/gfx/win | |
| parent | 8ce46c7881a3296187c7dd27afb581f84f4b27a7 (diff) | |
| download | chromium_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 'ui/gfx/win')
| -rw-r--r-- | ui/gfx/win/window_impl.cc | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/ui/gfx/win/window_impl.cc b/ui/gfx/win/window_impl.cc index e267f72..94e315c 100644 --- a/ui/gfx/win/window_impl.cc +++ b/ui/gfx/win/window_impl.cc @@ -291,6 +291,10 @@ LRESULT CALLBACK WindowImpl::WndProc(HWND hwnd, UINT message, WPARAM w_param, LPARAM l_param) { + // TODO(vadimt): Remove ScopedTracker below once crbug.com/440919 is fixed. + tracked_objects::ScopedTracker tracking_profile( + FROM_HERE_WITH_EXPLICIT_FUNCTION("440919 WindowImpl::WndProc")); + if (message == WM_NCCREATE) { CREATESTRUCT* cs = reinterpret_cast<CREATESTRUCT*>(l_param); WindowImpl* window = reinterpret_cast<WindowImpl*>(cs->lpCreateParams); |