You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I collect multiple record sessions via Start Recording (WebUSB) the trace gets accumulated. Say I collect 10 seconds, then wait a minute and collect another 10 seconds (with possibly different settings), then the trace covers 80 seconds. And trace_to_text shows that it contains the content of both sessions. I only see this when using the socket connection (AdbSocketConsumerPort), not when using AdbConsumerPort or when collecting via command line. Is this known behavior or a bug (well or both?). This is with a custom device, but nothing customized in this area.
This was causing a bug where traces from multiple consecutive
ADB tracing sessions were inadvertently concatenated together,
usually with a huge time gap between them.
Bug: 161917570, #37
Change-Id: Ie3a8ed8f3b8a1599a09da750869f5c35686e4093
When I collect multiple record sessions via Start Recording (WebUSB) the trace gets accumulated. Say I collect 10 seconds, then wait a minute and collect another 10 seconds (with possibly different settings), then the trace covers 80 seconds. And trace_to_text shows that it contains the content of both sessions. I only see this when using the socket connection (AdbSocketConsumerPort), not when using AdbConsumerPort or when collecting via command line. Is this known behavior or a bug (well or both?). This is with a custom device, but nothing customized in this area.
Was discussed on discord:
https://discord.com/channels/629013440635207702/629013441096450058/725016433481744504
The issue appears to be that we reuse the traceProtoWriter (a protobuf.Writer) in adb_socket_controller.ts, AdbSocketConsumerPort class.
The text was updated successfully, but these errors were encountered: