|Summary:||[chromium] Content and render surface textures not freed when compositor context destroyed|
|Product:||WebKit||Reporter:||James Robinson <jamesr>|
|Component:||New Bugs||Assignee:||James Robinson <jamesr>|
|Severity:||Normal||CC:||enne, kbr, vangelis, webkit.review.bot|
|Version:||528+ (Nightly build)|
Description James Robinson 2011-08-19 14:08:23 PDT
[chromium] Content and render surface textures not freed when compositor context destroyed
Comment 2 James Robinson 2011-08-19 14:22:45 PDT
We talked some in person about how to get better automated testing for stuff like this. I think the general thinking is that we need a way to test the compositing path with either a mock GraphicsContext3D or something lower-level to verify that we're actually releasing all of the resources we create.
Comment 3 Adrienne Walker 2011-08-20 12:49:22 PDT
Unofficially, looks good to me.
Comment 4 Kenneth Russell 2011-08-22 10:59:13 PDT
Comment on attachment 104563 [details] Patch rs=me
Comment 5 WebKit Review Bot 2011-08-22 11:19:11 PDT
Comment on attachment 104563 [details] Patch Clearing flags on attachment: 104563 Committed r93523: <http://trac.webkit.org/changeset/93523>
Comment 6 WebKit Review Bot 2011-08-22 11:19:15 PDT
All reviewed patches have been landed. Closing bug.