diff options
| author | vmpstr@chromium.org <vmpstr@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-05-02 23:22:03 +0000 |
|---|---|---|
| committer | vmpstr@chromium.org <vmpstr@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-05-02 23:22:03 +0000 |
| commit | f9e13ada454bb69df7000b37318447a593d3ca3d (patch) | |
| tree | 18e9d8475e8a46ec3800f220164a0ad59170bdde /cc/resources/tile_manager.cc | |
| parent | 1daeb245db5d3460ceb5ef206dfa3c2ad5ac76e8 (diff) | |
| download | chromium_src-f9e13ada454bb69df7000b37318447a593d3ca3d.zip chromium_src-f9e13ada454bb69df7000b37318447a593d3ca3d.tar.gz chromium_src-f9e13ada454bb69df7000b37318447a593d3ca3d.tar.bz2 | |
cc: Fix numbers that we report to the HUD
We seem to be reporting the whole memory limit as unreleasable. In
reality the memory limit shouldn't play a role in what we have
allocated, whether it is releasable or not.
BUG=369481
R=reveman
Review URL: https://codereview.chromium.org/266003003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@267959 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'cc/resources/tile_manager.cc')
| -rw-r--r-- | cc/resources/tile_manager.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/cc/resources/tile_manager.cc b/cc/resources/tile_manager.cc index 38948c3..d8fb17d 100644 --- a/cc/resources/tile_manager.cc +++ b/cc/resources/tile_manager.cc @@ -963,7 +963,7 @@ void TileManager::AssignGpuMemoryToTiles( memory_stats_from_last_assign_.bytes_allocated = hard_bytes_allocatable - hard_bytes_left; memory_stats_from_last_assign_.bytes_unreleasable = - hard_bytes_allocatable - bytes_releasable_; + resource_pool_->acquired_memory_usage_bytes() - bytes_releasable_; memory_stats_from_last_assign_.bytes_over = bytes_that_exceeded_memory_budget; } |