Thanks pkasting@ for trying this with http://src.chromium.org/viewvc/chrome?view=rev&revision=34108
But as the page cyclers dashboard seem to confirm, this is still a issue... :-( http://build.chromium.org/buildbot/perf/xp-release-dual-core/moz/report.html?history=150 BYE SAD :-( On Dec 8, 6:25 pm, MAD <m...@chromium.org> wrote: > I would love to try this... > > Let me know if somebody else is on it, otherwise, I will give it a > shot... > > BYE > MAD > > On Dec 7, 11:36 pm, Darin Fisher <da...@chromium.org> wrote: > > > > > On Mon, Dec 7, 2009 at 8:31 PM, Peter Kasting <pkast...@google.com> wrote: > > > On Mon, Dec 7, 2009 at 8:15 PM, Darin Fisher <da...@chromium.org> wrote: > > > >> Chrome now supports a handy command line flag that'll show you the > > >> regions > > >> of the > > >> page that are being re-painted. This can be helpful if you are tracking > > >> down repaint > > >> issues. > > > >> $ chrome --show-paint-rects > > > >> It's interesting to see what causes large re-paints ;-) > > > > I would love to see someone enable the window resize gripper on Windows > > > (which has never been enabled due to repaint perf issues) and start using > > > this flag to figure out what's up. > > > > Added incentive: maybe Darin's repaint coalescing work has eliminated the > > > performance problems of this code and we can just turn it on. > > > > PK > > > Yeah, I suspect that we should be able to re-enable the window resize > > gripper now. > > > -Darin -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
