Chrome Version: ToT
OS: Confirmed WIndows and Linux, probably all
What steps will reproduce the problem?
(1) Add code to catch recursion in the various UMA and UKM recording code in local_frame-view.
(2) Note that we hit the checks a lot. Also, UMA results showed a big jump in times when UMA reporting aggegrated all BeginMainFrame work, suggested we do Style,Layout,PrePaint,Paint and COmpositing multiple times per frame, sometimes.
What is the expected result?
There is absolutely no reason to paint more than once for a given frame in a given main frame time (or at least very rare reasons). Style and Layout does need to be done for some size negotiations, but painting is not required for that.
What happens instead?
We do more than one of everything inside UpdateLifecycle*.
Comment 1 by chrishtr@chromium.org
, Oct 17