Issue 561443002: Ouptut oldLocation and newLocation in trace of paint invalidation

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Issue 561443002: Ouptut oldLocation and newLocation in trace of paint invalidation (Closed)

Created:
6 years, 3 months ago by Xianzhu

Modified:
6 years, 3 months ago

Reviewers:
leviw_travelin_and_unemployed, pdr., esprehn

CC:
blink-reviews, blink-reviews-rendering, zoltan1, eae+blinkwatch, leviw+renderwatch, jchaffraix+rendering, rune+blink

Base URL:
svn://svn.chromium.org/blink/trunk

Project:
blink

Visibility:
Public.

More Reviews

Description

Ouptut oldLocation and newLocation in trace of paint invalidation I found that InvalidationLocationChange is a very frequent invalidation reason for some repaint storms. The invalidation is because the location (from the paint invalidation container) of the render object changed since the last invalidation. It will be helpful to know how the location changes when debugging repaint storms. Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=181759