contentTracing.setWatchEvent/cancelWatchEvent is removed
This commit is contained in:
parent
0a91779dfa
commit
d8e9432b0d
5 changed files with 0 additions and 55 deletions
|
@ -163,17 +163,3 @@ request the `callback` will be called with a file that contains the traced data.
|
|||
Get the maximum usage across processes of trace buffer as a percentage of the
|
||||
full state. When the TraceBufferUsage value is determined the `callback` is
|
||||
called.
|
||||
|
||||
### `contentTracing.setWatchEvent(categoryName, eventName, callback)`
|
||||
|
||||
* `categoryName` String
|
||||
* `eventName` String
|
||||
* `callback` Function
|
||||
|
||||
`callback` will be called every time the given event occurs on any
|
||||
process.
|
||||
|
||||
### `contentTracing.cancelWatchEvent()`
|
||||
|
||||
Cancel the watch event. This may lead to a race condition with the watch event
|
||||
callback if tracing is enabled.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue