memlog: Use browser to broker/restrict access to Profiling Service |
|||
Issue descriptionCurrently, any child process can request a Memlog interface and have the ServiceManager spin up the profiling process. Either add a MemlogProvider interface that the Browser exposes which passes the ConnectRequest to the actual service. This would let the browser examine internal state to determine whether or not it should spin up the profiling process. Alternately, expose a MemlogTarget interface in from each child process that the browser can call to insert a logging command after startup. Goals: (a) Allow the start/stop button to start/stop the profiling process (b) Allow profiling of children very early on in their startup.
,
Aug 8 2017
,
Aug 14 2017
Switching the API to use a broker was done here: https://chromium-review.googlesource.com/c/602526 The CL in question supports "starting" for (a), but the UI isn't actually hooked up. This is unrelated to (b). (a) and (b) seem like they're not part of the MVP.
,
Aug 14 2017
Okay. Closing this out and creating 2 separate bugs. 755241 - start/stop 755243 - early tracing of processes. |
|||
►
Sign in to add a comment |
|||
Comment 1 by erikc...@chromium.org
, Aug 2 2017