On Fri, Nov 27, 2009 at 5:43 PM, Kenneth Russell <k...@chromium.org> wrote: > http://code.google.com/p/chromium/issues/detail?id=21921 I observed > that on Windows that when the Chrome window is resized, a Skia canvas > the size of the entire window is allocated and discarded in order to > paint the window background. I don't think this happens during normal > repainting operations but is probably one cause of allocation > thrashing of these objects. If it would be helpful I can try to > reconstruct where this happens but others on this list probably know > where it is off the top of their heads.
When resizing, we need to repaint everything so we'll allocate a TransportDIB that is large enough to paint the whole window. TransportDIBs are cached at both ends it'll persist for a few seconds. If the window keeps getting large, then the old TransportDIB will be too small now and we'll allocate a new one. I think there's a little headroom added when we allocate, so hopefully we don't reallocate on every single frame, but if repaint takes a while then it's possible. AGL -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev