diff options
| author | jar@chromium.org <jar@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-10-24 18:55:16 +0000 |
|---|---|---|
| committer | jar@chromium.org <jar@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-10-24 18:55:16 +0000 |
| commit | 84baeca622c2d87c6a0aaf86e7a8362efe56fb25 (patch) | |
| tree | 7d15d6f00ae15785e1097d2fd5a7eb8053f90b0f /views | |
| parent | 620e0190cea3663581dd91b6f6bc61bd3c7ae02d (diff) | |
| download | chromium_src-84baeca622c2d87c6a0aaf86e7a8362efe56fb25.zip chromium_src-84baeca622c2d87c6a0aaf86e7a8362efe56fb25.tar.gz chromium_src-84baeca622c2d87c6a0aaf86e7a8362efe56fb25.tar.bz2 | |
Support JSON encoding of data for about:tracking information
I also fought a terrible (but educational) fight with Thread Local Store, and its ability to do cleanup (call destructors) at thread exit (notably applicable to Worker Threads). Thta is why there were soooo many test bot runs and tiny checkins. I now have a plan in mind that won't rely on that functionality. The code seems to work cross-platform, but if I have trouble with Linux, I'll repeatedly leak ThreadData contexts temporarily on that platform. Given that the code is only enabled under Debug, this is not yet a real problem.
Each CL I write for this code also includes a bunch of cleanup. In this case, I changed the Write() methods to WriteHTML(), since I didn't want any confusion with JSON writing etc. I also did a bunch of tiny cleanups which should not have changed what the code does.
r=rtenneti
Review URL: http://codereview.chromium.org/8313013
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@106952 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'views')
0 files changed, 0 insertions, 0 deletions