Bug 100027

Summary: [chromium] Remove unused GraphicsContext3DPrivate memory management
Product: WebKit Reporter: Christopher Cameron <ccameron>
Component: New BugsAssignee: Nobody <webkit-unassigned>
Status: RESOLVED WONTFIX    
Severity: Normal CC: jamesr
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch jamesr: review-

Christopher Cameron
Reported 2012-10-22 13:59:36 PDT
[chromium] Remove unused GraphicsContext3DPrivate memory management
Attachments
Patch (4.63 KB, patch)
2012-10-22 14:01 PDT, Christopher Cameron
jamesr: review-
Christopher Cameron
Comment 1 2012-10-22 14:01:36 PDT
Christopher Cameron
Comment 2 2012-10-22 14:23:26 PDT
Simple change, removing dead code.
James Robinson
Comment 3 2012-10-22 15:19:01 PDT
Comment on attachment 169979 [details] Patch 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?
Christopher Cameron
Comment 4 2012-10-22 15:45:16 PDT
Comment on attachment 169979 [details] Patch 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.
James Robinson
Comment 5 2012-10-22 15:50:27 PDT
The ganesh-owned context is used for things like canvas and filters, which aren't uniquely associated with any given tabs and thus don't really have clear notions of visibility. Anyway, looks like this code can't be killed just yet.
Christopher Cameron
Comment 6 2012-10-22 15:51:05 PDT
(In reply to comment #5) > The ganesh-owned context is used for things like canvas and filters, which aren't uniquely associated with any given tabs and thus don't really have clear notions of visibility. Anyway, looks like this code can't be killed just yet. Yeah, I'll keep my finger off of the trigger for now.
Note You need to log in before you can comment on or make changes to this bug.