[Webkit-unassigned] [Bug 100027] [chromium] Remove unused GraphicsContext3DPrivate memory management
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Oct 22 15:44:13 PDT 2012
https://bugs.webkit.org/show_bug.cgi?id=100027
--- Comment #4 from Christopher Cameron <ccameron at chromium.org> 2012-10-22 15:45:16 PST ---
(From update of attachment 169979)
View in context: https://bugs.webkit.org/attachment.cgi?id=169979&action=review
>> Source/WebCore/platform/chromium/support/GraphicsContext3DPrivate.cpp:-110
>> - m_context->setTextureCacheLimits(maxGaneshTextureCacheCount, maxGaneshTextureCacheBytes);
>
> This appears to actually do something, at least in theory. Do we never use this callback for canvas today? Do you have a replacement in mind for managing ganesh' texture use?
I ran a bunch more experiments, and did manage to get this to do something -- a canvas can manage to get a hint to drop textures if it is in a share group with a renderer that is not "hibernated" (not visible for a long time). I guess it's safe to leave this for now. It would be preferable for this to get visibility information directly, and act on that, rather than going through this roundabout path.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list