Capture/Replay: Don't capture XFB 0 in MEC.

This will only add an extra unused XFB object. Noticed when capturing from the T-Rex replay. Bug: angleproject:5134 Change-Id: Ia368f9e9f59f9ea7473ac88928a413001fa99496 Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2449157 Commit-Queue: Jamie Madill <jmadill@chromium.org> Reviewed-by: Courtney Goeltzenleuchter <courtneygo@google.com> Reviewed-by: Cody Northrop <cnorthrop@google.com>

Capture/Replay: Don't capture XFB 0 in MEC.
8608b402 · Jamie Madill · Commit Bot · 0ff24ae0 · 8608b402
Commit 8608b402 authored Oct 04, 2020 by Jamie Madill Committed by Commit Bot Oct 05, 2020
Hide whitespace changes
Inline Side-by-side

Showing with 7 additions and 0 deletions

FrameCapture.cpp src/libANGLE/FrameCapture.cpp +7 -0

No files found.
--- a/src/libANGLE/FrameCapture.cpp
+++ b/src/libANGLE/FrameCapture.cpp
@@ -2954,6 +2954,13 @@ void CaptureMidExecutionSetup(const gl::Context *context,
    for (const auto &xfbIter : xfbMap)
    {
        gl::TransformFeedbackID xfbID = {xfbIter.first};
+
+        // Do not capture the default XFB object.
+        if (xfbID.value == 0)
+        {
+            continue;
+        }
+
        cap(CaptureGenTransformFeedbacks(replayState, true, 1, &xfbID));
        MaybeCaptureUpdateResourceIDs(setupCalls);