From 0006e95b207be0bca6a8e6850e2d1f5147b453e4 Mon Sep 17 00:00:00 2001 From: danakj Date: Fri, 7 Aug 2015 17:36:54 -0700 Subject: cc: Use occlusion for deciding raster/eviction priorities in browser The browser compositor should use occlusion to allow lots of overlapping windows to take up less memory. This reduces our memory consumption in ash a bit. Though, the window UI is not considered opaque currently, so more memory is still used than could be otherwise. R=enne, vmpstr CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel Review URL: https://codereview.chromium.org/1277053002 Cr-Commit-Position: refs/heads/master@{#342493} --- cc/tiles/prioritized_tile.cc | 1 + 1 file changed, 1 insertion(+) (limited to 'cc/tiles/prioritized_tile.cc') diff --git a/cc/tiles/prioritized_tile.cc b/cc/tiles/prioritized_tile.cc index 67f33c9..2e0246c 100644 --- a/cc/tiles/prioritized_tile.cc +++ b/cc/tiles/prioritized_tile.cc @@ -33,6 +33,7 @@ void PrioritizedTile::AsValueInto(base::trace_event::TracedValue* value) const { value->BeginDictionary("combined_priority"); priority().AsValueInto(value); + value->SetBoolean("is_occluded", is_occluded_); value->EndDictionary(); value->SetString("resolution", TileResolutionToString(priority().resolution)); -- cgit v1.1