diff options
| author | peria@chromium.org <peria@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-01-28 18:37:25 +0000 |
|---|---|---|
| committer | peria@chromium.org <peria@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-01-28 18:37:25 +0000 |
| commit | 7c900e36bebd7fd6696637b3a8c6820644521170 (patch) | |
| tree | 09c8aab321fb1f2a3283626805d0c9892e682b75 /ppapi/ppapi_proxy.gypi | |
| parent | 9d2b12eadc8f57859ac8613e1cd28388fa098bd9 (diff) | |
| download | chromium_src-7c900e36bebd7fd6696637b3a8c6820644521170.zip chromium_src-7c900e36bebd7fd6696637b3a8c6820644521170.tar.gz chromium_src-7c900e36bebd7fd6696637b3a8c6820644521170.tar.bz2 | |
Before this CL, chrome://memory-internals stops listing up
processes, if a "Tab" process does not have histories.
This CL fix it with following changes.
1) Check if the index 'history' exists before accessing it.
2) Changed the order of updating, from
> process table -> extension table -> OS and uptime -> JSON
to
> JSON -> OS and uptime -> process table -> extension table,
because the JSON string is the original data, and tables
may contain unexpected bugs. If the JSON is shown, it is
easy to find why an update stops working.
BUG=338451,309913
TEST=Open chrome://memory-internals
NOTRY=true
Review URL: https://codereview.chromium.org/148233005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@247475 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'ppapi/ppapi_proxy.gypi')
0 files changed, 0 insertions, 0 deletions