[Webkit-unassigned] [Bug 106842] adding support for DiscardablePixelRef for caching lazily decoded images

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Jan 25 13:58:27 PST 2013


https://bugs.webkit.org/show_bug.cgi?id=106842





--- Comment #57 from Min Qin <qinmin at chromium.org>  2013-01-25 14:00:21 PST ---
(In reply to comment #56)
> (In reply to comment #55)
> > > The question is which system is responsible for making policy decisions.  Do you want to limit how much ashmem is used on platforms that support it?  If so, what limits do you want to have and how do you want them enforced?
> > 
> > There is a file descriptor limit of 1024, we currently use 128 in this case. 
> > Grace said don't use more than 1G of ashmem memory.
> 
> OK - but are those limits associated with the platform (i.e. global), or with a specific instance of an image decoding store?  It sounds like both of these limits are platform limitations, so they should be implemented by the implementation of WebDiscardableMemory, since no single caller of the API can be aware of all of the possibly users of it.

I think they are platform limitations. 
Putting it in WebDiscardableMemory seems ok, I will put 2 functions there and have the actual value defined in web_discardable_memory_impl

-- 
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