Stats collection for CAPS

CAPS aims to provide contextual information about a particular
crash, specifically what other processes where there at the
time of the crash.

Our current approach relies on the task manager which we activate
and wait until it gathers information about the existing resources
and then query, generate a json from it which we write to a file
which in the actual product will be a pipe connected to the
CAPS crash service process.

the JSON hierarchy is as follows :

{
  "os": { "arch", "name", "version" }
  "process": { pid : { "memory" : {}, "tabs" [], "uptime" }, ... pid : {} }
  "system" : { "cpu" : {}, "memory" : {} }
}

A test harness for this code in a follow up CL.

BUG=447073
TEST=none

Review URL: https://codereview.chromium.org/1000433004

Cr-Commit-Position: refs/heads/master@{#320357}

0 files changed, 0 insertions, 0 deletions