From 4258df38e642ea2f0808865343cfcb46ceb2b3dc Mon Sep 17 00:00:00 2001 From: Philipp Hancke Date: Fri, 30 Oct 2020 10:53:03 +0100 Subject: [PATCH] doc: mention video_replay tool for reporting video bugs No-Try: true Bug: None Change-Id: I1dafa3ad50f04080be8a0542b8f8bf79a7de7f6f Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/190982 Reviewed-by: Mirko Bonadei Commit-Queue: Philipp Hancke Cr-Commit-Position: refs/heads/master@{#32531} --- docs/bug-reporting.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/bug-reporting.md b/docs/bug-reporting.md index 764d78f688..885d68008f 100644 --- a/docs/bug-reporting.md +++ b/docs/bug-reporting.md @@ -102,6 +102,10 @@ Anyone with a [Google account][1] can file bugs in the Chrome and WebRTC tracker want to try [a bisect](https://www.chromium.org/developers/bisect-builds-py) to identify the commit that changed the behaviour. + * For **video problems**, e.g. artifacts or decoder failures, a rtpdump file + with the unencrypted RTP traffic. This can by replayed using the video_replay + tool from the rtc_tools directory. + ### Filing a Security Bug The WebRTC team takes security very seriously. If you find a vulnerability in