| commit | f9e13ada454bb69df7000b37318447a593d3ca3d | |
| author | vmpstr@chromium.org <vmpstr@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | |
| Fri, 2 May 2014 23:22:03 +0000 (2 23:22 +0000) | ||
| committer | vmpstr@chromium.org <vmpstr@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | |
| Fri, 2 May 2014 23:22:03 +0000 (2 23:22 +0000) | ||
| tree | 18e9d8475e8a46ec3800f220164a0ad59170bdde | treesnapshot (tar.gz zip) |
| parent | 1daeb245db5d3460ceb5ef206dfa3c2ad5ac76e8 | commitdiff |
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
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
| cc/resources/tile_manager.cc | diffblobblamehistory |