diff options
| author | mnaganov@chromium.org <mnaganov@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-03-13 13:09:10 +0000 |
|---|---|---|
| committer | mnaganov@chromium.org <mnaganov@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-03-13 13:09:10 +0000 |
| commit | d64bbadf8de48fab8dafa5874f51f5ae99c588cc (patch) | |
| tree | 531192b1946502eccf6b8fd98ecdeb286fb5ba1c /chrome/browser/sync/test/integration/sync_test.cc | |
| parent | 598b0a3dbf9d5d5b4d56597def445bb2b71f7d13 (diff) | |
| download | chromium_src-d64bbadf8de48fab8dafa5874f51f5ae99c588cc.zip chromium_src-d64bbadf8de48fab8dafa5874f51f5ae99c588cc.tar.gz chromium_src-d64bbadf8de48fab8dafa5874f51f5ae99c588cc.tar.bz2 | |
Remove --enable-memory-info flag
Chrome exposes quantized rate-limited information about memory through
'window.performance.memory'. This should be enough for the majority of web
developers. Developers who need more detailed data can use tools like Telemetry
to obtain JS heap size status via DevTools remote debugging protocol.
BUG=350339
TBR=palmer@chromium.org
Review URL: https://codereview.chromium.org/192653002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@256807 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/sync/test/integration/sync_test.cc')
0 files changed, 0 insertions, 0 deletions