This bug is created based on bug 1127170. If we move the display list profiler tracing from refresh driver to nsViewManager::ProcessPendingUpdates, then we can capture more use cases related to displaylist processing. Copy content from bug 1127170 comment 9. From the profiler in comment 6, the first long transaction loading of homescreen didn't display the 'DisplayList' Marker because this pending update is triggered from , not from refresh driver tick function. https://dxr.mozilla.org/mozilla-central/source/view/nsViewManager.cpp#678 https://dxr.mozilla.org/mozilla-central/source/layout/base/nsRefreshDriver.cpp#1708
BTW, this bug also requires some changes in cleopatra to display the 'displaylist' marker outside refresh driver.
No longer blocks: 1127170
Assignee: nobody → pchang
Status: NEW → ASSIGNED
Attachment #8569736 - Flags: review?(bgirard)
If I always bypass this checking in , I can see the displaylist marker which is not triggered from refresh driver. I will submit patch for cleopatra later. https://github.com/bgirard/cleopatra/blob/master/js/parserWorker.js#L2334
Comment on attachment 8569736 [details] [diff] [review] Move the displaylist tracing inside nsViewManager::ProcessPendingUpdates Seems reasonable. Passing to :mattwoodrow who knows the code better if it's a good boundary point or not.
Attachment #8569736 - Flags: review?(matt.woodrow) → review+
Remove redundant new line and update reviewers.
Build pass for all platform. https://treeherder.mozilla.org/#/jobs?repo=try&revision=b7dd912bca62
You need to log in before you can comment on or make changes to this bug.