|
@@ -81,48 +81,6 @@ Trace data will be written into `resultFilePath` if it is not empty or into a
|
|
|
temporary file. The actual file path will be passed to `callback` if it's not
|
|
|
`null`.
|
|
|
|
|
|
-### `contentTracing.startMonitoring(options, callback)`
|
|
|
-
|
|
|
-* `options` Object
|
|
|
- * `categoryFilter` String
|
|
|
- * `traceOptions` String
|
|
|
-* `callback` Function
|
|
|
-
|
|
|
-Start monitoring on all processes.
|
|
|
-
|
|
|
-Monitoring begins immediately locally and asynchronously on child processes as
|
|
|
-soon as they receive the `startMonitoring` request.
|
|
|
-
|
|
|
-Once all child processes have acknowledged the `startMonitoring` request the
|
|
|
-`callback` will be called.
|
|
|
-
|
|
|
-### `contentTracing.stopMonitoring(callback)`
|
|
|
-
|
|
|
-* `callback` Function
|
|
|
-
|
|
|
-Stop monitoring on all processes.
|
|
|
-
|
|
|
-Once all child processes have acknowledged the `stopMonitoring` request the
|
|
|
-`callback` is called.
|
|
|
-
|
|
|
-### `contentTracing.captureMonitoringSnapshot(resultFilePath, callback)`
|
|
|
-
|
|
|
-* `resultFilePath` String
|
|
|
-* `callback` Function
|
|
|
- * `resultFilePath` String
|
|
|
-
|
|
|
-Get the current monitoring traced data.
|
|
|
-
|
|
|
-Child processes typically cache trace data and only rarely flush and send
|
|
|
-trace data back to the main process. This is because it may be an expensive
|
|
|
-operation to send the trace data over IPC and we would like to avoid unneeded
|
|
|
-runtime overhead from tracing. So, to end tracing, we must asynchronously ask
|
|
|
-all child processes to flush any pending trace data.
|
|
|
-
|
|
|
-Once all child processes have acknowledged the `captureMonitoringSnapshot`
|
|
|
-request the `callback` will be called with a file that contains the traced data.
|
|
|
-
|
|
|
-
|
|
|
### `contentTracing.getTraceBufferUsage(callback)`
|
|
|
|
|
|
* `callback` Function
|