DescriptionDevTools: use async operation id instead of AsyncCallChain
Debugger agent API now allows to assign asinc operation a unique identifier and use it to trace that operation. Async operation id returned by traceAsyncOperationStarting is always valid and greater than zero (HashMap would crash on store/lookup of special values like -1 and 0 in it, to avoid that we just make sure that the key is always >0) hence there is no need to check if its valid or not anymore.
If the client needs to report that a callback is starting executing but its operation id is unknown (e.g. because the tracking was off when the operation started) it just passes InspectorDebuggerAgent::unknownAsyncOperationId as it id.
BUG=439376
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=188733
Patch Set 1 #
Total comments: 20
Patch Set 2 : Addressed comments #Patch Set 3 : Remove unnecessary checks as operationId is always valid now #Patch Set 4 : Rebase #Patch Set 5 : Fixed assert #
Total comments: 6
Patch Set 6 : Addressed comments #
Total comments: 2
Messages
Total messages: 14 (4 generated)
|