D3D11: Fix potential invalid VAO access in dispatch.

In some instances running a dispatch call could lead to accessing an invalid VAO pointer. This seemed to be tied to switching Contexts. Fix the bug by invalidating the cache pointers on Context switch. Note that it seems this bug can only affect ES 3.1+ Contexts. Bug: angleproject:3349 Change-Id: Ib712bcc29215b3fd1c8b7eb0cbd70dea649b3cfc Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1594289Reviewed-by: Jamie Madill <jmadill@chromium.org> Commit-Queue: Jamie Madill <jmadill@chromium.org>

D3D11: Fix potential invalid VAO access in dispatch.
6f0c5b8d · Jamie Madill · Commit Bot · 62742f9e · 6f0c5b8d
Commit 6f0c5b8d authored May 04, 2019 by Jamie Madill Committed by Commit Bot May 04, 2019
Hide whitespace changes
Inline Side-by-side

Showing with 5 additions and 0 deletions

StateManager11.cpp src/libANGLE/renderer/d3d/d3d11/StateManager11.cpp +5 -0

No files found.
--- a/src/libANGLE/renderer/d3d/d3d11/StateManager11.cpp
+++ b/src/libANGLE/renderer/d3d/d3d11/StateManager11.cpp
@@ -1701,6 +1701,11 @@ angle::Result StateManager11::onMakeCurrent(const gl::Context *context)
        }
    }

+    // Reset the cache objects.
+    mProgramD3D    = nullptr;
+    mVertexArray11 = nullptr;
+    mFramebuffer11 = nullptr;
+
    return angle::Result::Continue;
 }