Skip deletion of null framebuffers.

It's valid to have a map entry that is null to represent a framebuffer that has been generated but never bound. This was causing crashes after dEQP pbo tests were run during dEQP shutdown. BUG=angleproject:1149 Change-Id: Idcedac23e5c4e17ed025b10c2939572b394d3aec Reviewed-on: https://chromium-review.googlesource.com/296962Reviewed-by: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Jamie Madill <jmadill@chromium.org> Tested-by: Geoff Lang <geofflang@chromium.org>

Skip deletion of null framebuffers.
f622792b · Geoff Lang · 0db7b155 · f622792b
Commit f622792b authored Sep 04, 2015 by Geoff Lang
Hide whitespace changes
Inline Side-by-side

Showing with 1 addition and 1 deletion

Context.cpp src/libANGLE/Context.cpp +1 -1

No files found.
--- a/src/libANGLE/Context.cpp
+++ b/src/libANGLE/Context.cpp
@@ -155,7 +155,7 @@ Context::~Context()
    for (auto framebuffer : mFramebufferMap)
    {
        // Default framebuffer are owned by their respective Surface
-        if (framebuffer.second->id() != 0)
+        if (framebuffer.second != nullptr && framebuffer.second->id() != 0)
        {
            SafeDelete(framebuffer.second);
        }