Skip to main content

resource_cache_single_allocation_byte_limit

Function resource_cache_single_allocation_byte_limit 

pub fn resource_cache_single_allocation_byte_limit() -> Option<usize>
Expand description

When the cacheable entry is very large, adding it to the cache can cause most or all of the existing entries to be purged. To avoid this, a client can set a limit for a single allocation. If a cacheable entry would have been cached, but its size exceeds this limit, then it is not cached at all.

None is the default value, meaning Skia always attempts to cache entries.